← previous blocknext block →recent activity
Analyzing
Block #96,191,426
8 transactions · 5 stateful · 2026-08-15 11:27:36 UTC
Parallelism
63/100
Blocked
40%
Avg conflicts / tx
0.38
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #96,191,426 · 8 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
2w03w16w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xe624cb16…9dc0
0x34b655…2a6f
4 touches
1 conflict
0x66bdb4c2…7ea6
0x34b655…2a6f
4 touches
1 conflict
0x3e3f27ce…580c
0x34b655…2a6f
4 touches
1 conflict
0x03f717cd…62de
0x34b655…2a6f
4 touches
1 conflict
0xa94c3b09…26c7
0x34b655…2a6f
4 touches
1 conflict
0xa94c3b09…26c8
0x34b655…2a6f
4 touches
1 conflict
0x383ccd7d…3bc5
0x34b655…2a6f
4 touches
1 conflict
0xb6d7ed80…2dd2
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
1 conflict on slot 0xe624cb16a5…b69dc0
Audit this contract →
← previous block·next block →recent activity