← previous blocknext block →recent activity
Analyzing
Block #96,535,329
9 transactions · 8 stateful · 2026-08-16 16:17:35 UTC
Parallelism
67/100
Blocked
50%
Avg conflicts / tx
0.67
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #96,535,329 · 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
1w02w13w15w17w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x2a1705ef…ec8b
0x34b655…2a6f
6 touches
3 conflicts
0xb2fa1675…4e07
0x34b655…2a6f
6 touches
3 conflicts
0xb3fb9fb5…64db
0x34b655…2a6f
4 touches
1 conflict
0x4d143d3d…5331
0x34b655…2a6f
4 touches
1 conflict
0x898d9b8a…d1ef
0x34b655…2a6f
4 touches
1 conflict
0x35177414…c40a
0x34b655…2a6f
2 touches
0 conflicts
0x5939780d…8d2a
0x34b655…2a6f
2 touches
0 conflicts
0x835755fd…0fea
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
3 conflicts on slot 0x2a1705efc8…55ec8b
Audit this contract →
← previous block·next block →recent activity