← previous blocknext block →recent activity
Analyzing
Block #95,125,853
16 transactions · 15 stateful · 2026-08-11 17:52:52 UTC
Parallelism
63/100
Blocked
40%
Avg conflicts / tx
0.81
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #95,125,853 · 16 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
1w03w04w16w27w310w411w514w015w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x000bde1a…e123
0x34b655…2a6f
6 touches
3 conflicts
0x54d44f83…c160
0x34b655…2a6f
6 touches
3 conflicts
0x6ed3bed0…4d5f
0x34b655…2a6f
6 touches
3 conflicts
0xbcbf5d09…8bac
0x34b655…2a6f
6 touches
3 conflicts
0xc824469a…6425
0x34b655…2a6f
6 touches
3 conflicts
0x679705f0…4531
0x34b655…2a6f
4 touches
1 conflict
0xe7f77c59…a6c4
0x34b655…2a6f
4 touches
1 conflict
0x706c758c…2fdb
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
3 conflicts on slot 0x000bde1afc…91e123
Audit this contract →
← previous block·next block →recent activity