← previous blocknext block →recent activity
Analyzing
Block #96,514,305
15 transactions · 13 stateful · 2026-08-16 14:31:51 UTC
Parallelism
67/100
Blocked
38%
Avg conflicts / tx
0.53
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #96,514,305 · 15 txs across 5 waves · depth 5
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
2w03w05w16w27w310w411w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x5da59c2b…d7b2
0x34b655…2a6f
8 touches
6 conflicts
0x6254804c…a03b
0x34b655…2a6f
8 touches
6 conflicts
0xc824469a…641f
0x34b655…2a6f
8 touches
6 conflicts
0x00000000…00c9
0x34b655…2a6f
8 touches
6 conflicts
0xe3280296…788e
0x34b655…2a6f
7 touches
6 conflicts
0x3d8d3796…6a52
0x34b655…2a6f
7 touches
6 conflicts
0xd09e14b2…d3ab
0x34b655…2a6f
6 touches
3 conflicts
0xc824469a…6425
0x34b655…2a6f
6 touches
3 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
6 conflicts on slot 0x5da59c2b2f…b6d7b2
Audit this contract →
← previous block·next block →recent activity