← previous blocknext block →recent activity
Analyzing
Block #96,544,180
10 transactions · 7 stateful · 2026-08-16 17:02:06 UTC
Parallelism
80/100
Blocked
29%
Avg conflicts / tx
0.2
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #96,544,180 · 10 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
1w02w15w06w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x17f5dec8…3332
0x34b655…2a6f
4 touches
1 conflict
0xbcbf5d09…8bac
0x34b655…2a6f
4 touches
1 conflict
0x53f393fa…00b9
0x34b655…2a6f
4 touches
1 conflict
0x33649c4f…b327
0x34b655…2a6f
4 touches
1 conflict
0x2a07ec57…d89e
0x34b655…2a6f
2 touches
0 conflicts
0x4f44533d…c3a0
0x34b655…2a6f
2 touches
0 conflicts
0x6819f434…82c8
0x34b655…2a6f
2 touches
0 conflicts
0x7e5ea60a…c4a2
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 0x17f5dec852…2f3332
Audit this contract →
← previous block·next block →recent activity