← previous blocknext block →recent activity
Analyzing
Block #96,495,577
10 transactions · 9 stateful · 2026-08-16 12:57:23 UTC
Parallelism
70/100
Blocked
44%
Avg conflicts / tx
0.5
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #96,495,577 · 10 txs across 3 waves · depth 3
parallel ↔ serial
wave w0
wave w1
wave w2
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w03w14w16w07w19w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x34a1ee7e…fb20
0x34b655…2a6f
6 touches
3 conflicts
0xda6e0564…f576
0x968279…9342
4 touches
1 conflict
0xa23af321…0452
0x968279…9342
4 touches
1 conflict
0xa23af321…0454
0x968279…9342
4 touches
1 conflict
0xda6e0564…f573
0x968279…9342
4 touches
1 conflict
0xda6e0564…f574
0x968279…9342
4 touches
1 conflict
0x66bdb4c2…7ea6
0x34b655…2a6f
4 touches
1 conflict
0xae4a282a…f2ea
0x34b655…2a6f
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 0x34a1ee7e95…7cfb20
Audit this contract →
← previous block·next block →recent activity