← previous blocknext block →recent activity
Analyzing
Block #95,397,511
20 transactions · 18 stateful · 2026-08-12 16:52:03 UTC
Parallelism
60/100
Blocked
50%
Avg conflicts / tx
1.55
Longest chain
8 deep
Execution timeline
did this block parallelize well?
view
block #95,397,511 · 20 txs across 8 waves · depth 8
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
wave w7
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
6w07w18w29w310w411w512w613w7
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xf2a70d6a…8385
0x350035…7777
16 touches
28 conflicts
0x42041fec…bd86
0x754704…b603
6 touches
3 conflicts
0x0b000000…0002
0x000000…1000
2 touches
0 conflicts
0x18e2705b…5912
0x34b655…2a6f
2 touches
0 conflicts
0x222733a8…8e7a
0x34b655…2a6f
2 touches
0 conflicts
0x222733a8…8e7b
0x34b655…2a6f
2 touches
0 conflicts
0x278686dc…698d
0x34b655…2a6f
2 touches
0 conflicts
0x388a4c2f…9868
0x34b655…2a6f
2 touches
0 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: 0x35003555…c27777
28 conflicts on slot 0xf2a70d6ac1…c28385
Audit this contract →
← previous block·next block →recent activity