← previous blocknext block →recent activity
Analyzing
Block #96,652,072
12 transactions · 11 stateful · 2026-08-17 02:04:46 UTC
Parallelism
83/100
Blocked
36%
Avg conflicts / tx
0.33
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #96,652,072 · 12 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
1w02w13w07w19w111w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xcd6ccd20…c33e
0x34b655…2a6f
4 touches
1 conflict
0x0649b8e0…c704
0x34b655…2a6f
4 touches
1 conflict
0x19cbeea8…ecf3
0x34b655…2a6f
4 touches
1 conflict
0x22e0cc1d…ad0d
0x34b655…2a6f
4 touches
1 conflict
0x8b029a77…81e4
0x34b655…2a6f
4 touches
1 conflict
0xa0d3a786…91d9
0x34b655…2a6f
4 touches
1 conflict
0xbacde1a6…3a7c
0x34b655…2a6f
4 touches
1 conflict
0xca841faa…486a
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 0xcd6ccd2062…74c33e
Audit this contract →
← previous block·next block →recent activity