← previous blocknext block →recent activity
Analyzing
Block #95,034,053
20 transactions · 18 stateful · 2026-08-11 10:10:37 UTC
Parallelism
85/100
Blocked
17%
Avg conflicts / tx
0.2
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #95,034,053 · 20 txs across 3 waves · depth 3
parallel ↔ serial
wave w0
wave w1
wave w2
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
3w04w05w16w19w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x89c9306c…7a89
0x34b655…2a6f
6 touches
3 conflicts
0x3a921be0…779c
0x2a68ba…90c5
4 touches
1 conflict
0x2b54cadb…4425
0xd18b7e…414b
4 touches
1 conflict
0xc824469a…6425
0x34b655…2a6f
4 touches
1 conflict
0xe0e00683…e335
0x34b655…2a6f
4 touches
1 conflict
0xe22ab637…7a8e
0x34b655…2a6f
4 touches
1 conflict
0x0546b155…0373
0x40c49f…2af0
4 touches
1 conflict
0x3d9eb674…b3fb
0x754704…b603
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
3 conflicts on slot 0x89c9306c36…d37a89
Audit this contract →
← previous block·next block →recent activity