← previous blocknext block →recent activity
Analyzing
Block #105,539,089
14 transactions · 14 stateful · 2026-09-17 06:54:44 UTC
Parallelism
86/100
Blocked
14%
Avg conflicts / tx
0.14
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #105,539,089 · 14 txs across 2 waves · depth 2
parallel ↔ serial
wave w0
wave w1
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
9w010w011w113w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xba1edffb…323e
0x34b655…2a6f
4 touches
1 conflict
0xef5959a3…2a2f
0x34b655…2a6f
4 touches
1 conflict
0x1bf239bd…46ad
0x34b655…2a6f
4 touches
1 conflict
0x4188cc5f…2d2e
0x34b655…2a6f
4 touches
1 conflict
0x81b0a2e9…e388
0x34b655…2a6f
4 touches
1 conflict
0x3a3e7727…36c5
0x34ae4d…3fc5
2 touches
0 conflicts
0x5a409e7f…09b6
0x34ae4d…3fc5
2 touches
0 conflicts
0x62811193…1869
0x34ae4d…3fc5
2 touches
0 conflicts
What's blocking what?
Click any transaction in the timeline or graph to see which storage slots forced it to wait, and which later transactions it blocked.
The bottleneck
Throughput-killer: Perpl
1 conflict on slot 0xba1edffb42…64323e
Audit this contract →
← previous block·next block →recent activity