← previous blocknext block →recent activity
Analyzing
Block #95,392,412
11 transactions · 9 stateful · 2026-08-12 16:26:17 UTC
Parallelism
82/100
Blocked
22%
Avg conflicts / tx
0.18
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #95,392,412 · 11 txs across 2 waves · depth 2
parallel ↔ serial
wave w0
wave w1
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w07w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x16f8e14a…f6e4
0x34b655…2a6f
4 touches
1 conflict
0xe73b93bf…c0e1
0x34b655…2a6f
4 touches
1 conflict
0x22e0cc1d…ad0d
0x34b655…2a6f
4 touches
1 conflict
0xca841faa…486a
0x34b655…2a6f
4 touches
1 conflict
0x43fd3667…094b
0x34b655…2a6f
2 touches
0 conflicts
0x58bb2989…ad12
0x34b655…2a6f
2 touches
0 conflicts
0x59063527…7864
0x34b655…2a6f
2 touches
0 conflicts
0x691cfe2e…96cd
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: Perpl
1 conflict on slot 0x16f8e14aad…3ff6e4
Audit this contract →
← previous block·next block →recent activity