← previous blocknext block →recent activity
Analyzing
Block #101,966,236
24 transactions · 20 stateful · 2026-09-04 18:00:42 UTC
Parallelism
75/100
Blocked
40%
Avg conflicts / tx
0.5
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #101,966,236 · 24 txs across 6 waves · depth 6
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w16w011w112w214w015w118w221w322w423w5
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x51fc8795…126f
0x34b655…2a6f
6 touches
3 conflicts
0xd98b3c10…67b8
0x34b655…2a6f
6 touches
3 conflicts
0xb75367ff…a2b7
0x34b655…2a6f
6 touches
3 conflicts
0x84f3fd5a…503d
0xd32edf…ff58
5 touches
3 conflicts
0xbcc1b459…f94f
0x3bd359…433a
4 touches
1 conflict
0x00000000…0000
0xaa5de1…d330
4 touches
1 conflict
0x00000000…0002
0xaa5de1…d330
4 touches
1 conflict
0x00000000…0003
0xaa5de1…d330
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: Perpl
3 conflicts on slot 0x51fc8795c8…57126f
Audit this contract →
← previous block·next block →recent activity