← previous blocknext block →recent activity
Analyzing
Block #95,721,618
13 transactions · 12 stateful · 2026-08-13 20:04:05 UTC
Parallelism
54/100
Blocked
58%
Avg conflicts / tx
1.08
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #95,721,618 · 13 txs across 6 waves · depth 6
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
3w04w15w26w18w39w410w511w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x3cd98e7d…4628
0x34b655…2a6f
8 touches
6 conflicts
0xe2ca9bf2…8da8
0x34b655…2a6f
6 touches
3 conflicts
0xca841faa…486a
0x34b655…2a6f
6 touches
3 conflicts
0x3b6e959d…158f
0x34b655…2a6f
4 touches
1 conflict
0x434ca03c…9f46
0x34b655…2a6f
4 touches
1 conflict
0x482471ad…122f
0x34b655…2a6f
4 touches
1 conflict
0x4bfdcd51…9b58
0x34b655…2a6f
4 touches
1 conflict
0x5bdae4ca…5d23
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
6 conflicts on slot 0x3cd98e7d7b…254628
Audit this contract →
← previous block·next block →recent activity