← previous blocknext block →recent activity
Analyzing
Block #102,476,226
24 transactions · 19 stateful · 2026-09-06 13:05:06 UTC
Parallelism
83/100
Blocked
42%
Avg conflicts / tx
0.5
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #102,476,226 · 24 txs across 4 waves · depth 4
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w03w04w17w08w114w116w017w118w219w221w022w123w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x0ef74796…cd18
0x0a3323…0a3c
6 touches
3 conflicts
0x51fc8795…126f
0x34b655…2a6f
6 touches
3 conflicts
0xd98b3c10…67b8
0x34b655…2a6f
6 touches
3 conflicts
0xa060b594…669d
0x754704…b603
6 touches
3 conflicts
0x00000000…0000
0x834d94…8555
6 touches
3 conflicts
0x00000000…0004
0x834d94…8555
6 touches
3 conflicts
0xdede828e…ae39
0x834d94…8555
4 touches
1 conflict
0xdede828e…ae3a
0x834d94…8555
4 touches
1 conflict
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: 0x0a332311…6e0a3c
3 conflicts on slot 0x0ef74796d8…7ccd18
Audit this contract →
← previous block·next block →recent activity