← previous blocknext block →recent activity
Analyzing
Block #96,294,837
13 transactions · 13 stateful · 2026-08-15 20:07:44 UTC
Parallelism
85/100
Blocked
31%
Avg conflicts / tx
0.31
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #96,294,837 · 13 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
3w04w16w07w110w111w012w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xfe708efe…df34
0x34b655…2a6f
4 touches
1 conflict
0x67a51e00…b6b1
0x34b655…2a6f
4 touches
1 conflict
0x6859525f…4f99
0x34b655…2a6f
4 touches
1 conflict
0x7fe40a8d…59f8
0x34b655…2a6f
4 touches
1 conflict
0x9e089d27…ab74
0x34b655…2a6f
4 touches
1 conflict
0xc10b903d…2f54
0x34b655…2a6f
4 touches
1 conflict
0xca3f7973…e7e7
0x34b655…2a6f
4 touches
1 conflict
0xca3f7973…e7e8
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 0xfe708efe93…b8df34
Audit this contract →
← previous block·next block →recent activity