← previous blocknext block →recent activity
Analyzing
Block #95,522,669
18 transactions · 17 stateful · 2026-08-13 03:22:21 UTC
Parallelism
67/100
Blocked
59%
Avg conflicts / tx
1.39
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #95,522,669 · 18 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
1w04w15w26w07w18w29w310w411w513w216w317w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x1a5d321d…a474
0x34b655…2a6f
10 touches
10 conflicts
0xa1087a5c…66c4
0x754704…b603
10 touches
10 conflicts
0x11b69a7e…334e
0xee8c0e…1242
10 touches
10 conflicts
0x002fed35…79fa
0x2a68ba…90c5
10 touches
10 conflicts
0x42f376fa…6766
0x34b655…2a6f
8 touches
6 conflicts
0x12a25402…4467
0xa6afd3…d132
7 touches
6 conflicts
0x2697123c…8526
0x34b655…2a6f
6 touches
3 conflicts
0xe5bb3628…e5f1
0x34b655…2a6f
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
10 conflicts on slot 0x1a5d321d5d…0da474
Audit this contract →
← previous block·next block →recent activity