← previous blocknext block →recent activity
Analyzing
Block #96,560,739
9 transactions · 8 stateful · 2026-08-16 18:25:23 UTC
Parallelism
78/100
Blocked
13%
Avg conflicts / tx
0.11
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #96,560,739 · 9 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
5w06w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xf4c9a0df…dcd4
0x34b655…2a6f
4 touches
1 conflict
0xf4c9a0df…dcd5
0x34b655…2a6f
4 touches
1 conflict
0xb4a24b80…4103
0x34b655…2a6f
4 touches
1 conflict
0x84122bae…5359
0x34b655…2a6f
4 touches
1 conflict
0xd378f050…88e8
0x34b655…2a6f
4 touches
1 conflict
0x3f0a88e0…392e
0x34b655…2a6f
4 touches
1 conflict
0x77d7ceb1…7102
0x34b655…2a6f
2 touches
0 conflicts
0x9fd37234…2731
0x34b655…2a6f
2 touches
0 conflicts
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 0xf4c9a0dfc5…fcdcd4
Audit this contract →
← previous block·next block →recent activity