← previous blocknext block →recent activity
Analyzing
Block #96,279,205
14 transactions · 12 stateful · 2026-08-15 18:49:07 UTC
Parallelism
86/100
Blocked
25%
Avg conflicts / tx
0.21
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #96,279,205 · 14 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
2w03w15w06w111w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x513b0c80…d2d9
0x34b655…2a6f
4 touches
1 conflict
0x53a854a3…8db8
0x34b655…2a6f
4 touches
1 conflict
0x81561f70…fefd
0x34b655…2a6f
4 touches
1 conflict
0x846cd867…f36c
0x34b655…2a6f
4 touches
1 conflict
0x2d62181c…a99f
0x34b655…2a6f
4 touches
1 conflict
0xac2a0273…721b
0x34b655…2a6f
4 touches
1 conflict
0xca841faa…486a
0x34b655…2a6f
4 touches
1 conflict
0xf63c2a2b…bc5f
0x34b655…2a6f
4 touches
1 conflict
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 0x513b0c80f3…fbd2d9
Audit this contract →
← previous block·next block →recent activity