← previous blocknext block →recent activity
Analyzing
Block #95,636,366
13 transactions · 13 stateful · 2026-08-13 12:54:14 UTC
Parallelism
77/100
Blocked
31%
Avg conflicts / tx
0.38
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #95,636,366 · 13 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
5w06w17w08w19w210w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xac2a0273…721b
0x34b655…2a6f
6 touches
3 conflicts
0xe5ed2e34…678f
0x968279…9342
4 touches
1 conflict
0x2a81bc72…3b4c
0x968279…9342
4 touches
1 conflict
0x2a81bc72…3b4d
0x968279…9342
4 touches
1 conflict
0xe5ed2e34…678c
0x968279…9342
4 touches
1 conflict
0xe5ed2e34…678d
0x968279…9342
4 touches
1 conflict
0x08636046…e60f
0x34b655…2a6f
4 touches
1 conflict
0x4e58deff…c5d0
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 0xac2a02739b…81721b
Audit this contract →
← previous block·next block →recent activity