← previous blocknext block →recent activity
Analyzing
Block #96,447,970
10 transactions · 8 stateful · 2026-08-16 08:57:53 UTC
Parallelism
70/100
Blocked
38%
Avg conflicts / tx
0.3
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #96,447,970 · 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
1w05w06w17w18w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xadef9c8b…b921
0x968279…9342
4 touches
1 conflict
0xadef9c8b…b928
0x968279…9342
4 touches
1 conflict
0xadef9c8b…b926
0x968279…9342
4 touches
1 conflict
0xadef9c8b…b925
0x968279…9342
4 touches
1 conflict
0xadef9c8b…b922
0x968279…9342
4 touches
1 conflict
0x424934c8…f2f1
0x34b655…2a6f
4 touches
1 conflict
0x9ff6dd4d…e44d
0x34b655…2a6f
4 touches
1 conflict
0xac2a0273…721b
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: 0x96827978…f09342
1 conflict on slot 0xadef9c8b58…b6b921
Audit this contract →
← previous block·next block →recent activity