← previous blocknext block →recent activity
Analyzing
Block #95,593,091
21 transactions · 17 stateful · 2026-08-13 09:16:33 UTC
Parallelism
76/100
Blocked
47%
Avg conflicts / tx
0.71
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #95,593,091 · 21 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
3w04w15w07w19w210w011w112w217w018w219w320w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xd98b3c10…67b8
0x34b655…2a6f
8 touches
6 conflicts
0xf0f2b2ef…9283
0x968279…9342
6 touches
3 conflicts
0x5a3f030a…2621
0x968279…9342
6 touches
3 conflicts
0x5a3f030a…2622
0x968279…9342
6 touches
3 conflicts
0x5a3f030a…2625
0x968279…9342
6 touches
3 conflicts
0x5a3f030a…2626
0x968279…9342
6 touches
3 conflicts
0x5a3f030a…2628
0x968279…9342
6 touches
3 conflicts
0xf0f2b2ef…9280
0x968279…9342
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 0xd98b3c102b…ca67b8
Audit this contract →
← previous block·next block →recent activity