← previous blocknext block →recent activity
Analyzing
Block #95,582,486
14 transactions · 13 stateful · 2026-08-13 08:23:13 UTC
Parallelism
71/100
Blocked
31%
Avg conflicts / tx
0.36
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #95,582,486 · 14 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
2w05w16w112w213w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xd0919e62…a2a8
0x34b655…2a6f
6 touches
3 conflicts
0xeb721d02…7bfa
0x34b655…2a6f
4 touches
1 conflict
0xebc90a90…5930
0x34b655…2a6f
4 touches
1 conflict
0xd98b3c10…67b8
0x34b655…2a6f
4 touches
1 conflict
0x57be321f…fecc
0x34b655…2a6f
4 touches
1 conflict
0x82dd2252…e1ce
0x34b655…2a6f
4 touches
1 conflict
0xca841faa…486a
0x34b655…2a6f
4 touches
1 conflict
0x427dec7f…61c6
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
3 conflicts on slot 0xd0919e626f…7ea2a8
Audit this contract →
← previous block·next block →recent activity