← previous blocknext block →recent activity
Analyzing
Block #96,449,433
9 transactions · 7 stateful · 2026-08-16 09:05:14 UTC
Parallelism
67/100
Blocked
29%
Avg conflicts / tx
0.33
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #96,449,433 · 9 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
5w06w17w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xf9c7befd…e533
0x34b655…2a6f
4 touches
1 conflict
0x0460135c…98fd
0x34b655…2a6f
4 touches
1 conflict
0xa5c8cbd0…4891
0x34b655…2a6f
4 touches
1 conflict
0xb91ace84…d2cf
0x34b655…2a6f
4 touches
1 conflict
0xbcbf5d09…8bac
0x34b655…2a6f
4 touches
1 conflict
0xe9ba215a…1076
0x34b655…2a6f
4 touches
1 conflict
0xf9c7befd…e532
0x34b655…2a6f
4 touches
1 conflict
0x5f758480…3241
0x34b655…2a6f
3 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 0xf9c7befd83…4ce533
Audit this contract →
← previous block·next block →recent activity