← previous blocknext block →recent activity
Analyzing
Block #96,482,867
9 transactions · 9 stateful · 2026-08-16 11:53:26 UTC
Parallelism
56/100
Blocked
33%
Avg conflicts / tx
0.33
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #96,482,867 · 9 txs across 4 waves · depth 4
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w15w27w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xbde524f4…43bf
0x34b655…2a6f
4 touches
1 conflict
0xcbda32af…5a25
0x34b655…2a6f
4 touches
1 conflict
0xff196840…a453
0x34b655…2a6f
4 touches
1 conflict
0x02991b41…19e6
0x34b655…2a6f
2 touches
0 conflicts
0x081e86ec…551c
0x34b655…2a6f
2 touches
0 conflicts
0x11e44201…612d
0x34b655…2a6f
2 touches
0 conflicts
0x1565183a…e0a0
0x34b655…2a6f
2 touches
0 conflicts
0x2ff5b7c6…d8e6
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 0xbde524f475…b143bf
Audit this contract →
← previous block·next block →recent activity