← previous blocknext block →recent activity
Analyzing
Block #96,526,940
12 transactions · 11 stateful · 2026-08-16 15:35:24 UTC
Parallelism
58/100
Blocked
55%
Avg conflicts / tx
1.08
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #96,526,940 · 12 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
1w02w13w04w16w17w29w310w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x482471ad…122f
0x34b655…2a6f
8 touches
6 conflicts
0x600acf8b…4638
0x34b655…2a6f
6 touches
3 conflicts
0x97288dcc…09d7
0x34b655…2a6f
6 touches
3 conflicts
0xc824469a…6425
0x34b655…2a6f
6 touches
3 conflicts
0xca841faa…486a
0x34b655…2a6f
6 touches
3 conflicts
0xd66696e0…0842
0x34b655…2a6f
6 touches
3 conflicts
0xff196840…a453
0x34b655…2a6f
6 touches
3 conflicts
0x597fe175…795d
0x34b655…2a6f
5 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 0x482471adbb…39122f
Audit this contract →
← previous block·next block →recent activity