← previous blocknext block →recent activity
Analyzing
Block #95,396,398
13 transactions · 13 stateful · 2026-08-12 16:46:26 UTC
Parallelism
85/100
Blocked
31%
Avg conflicts / tx
0.31
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #95,396,398 · 13 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
2w03w14w05w16w112w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xd0fd6c76…ddaf
0x34b655…2a6f
4 touches
1 conflict
0x0759c8f2…8408
0x34b655…2a6f
4 touches
1 conflict
0x22e0cc1d…ad0d
0x34b655…2a6f
4 touches
1 conflict
0x482471ad…122f
0x34b655…2a6f
4 touches
1 conflict
0x4eef5ec8…7d2f
0x34b655…2a6f
4 touches
1 conflict
0x92fd8c8a…b2b8
0x34b655…2a6f
4 touches
1 conflict
0xba352368…cbf1
0x34b655…2a6f
4 touches
1 conflict
0xbf9d3917…2850
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
1 conflict on slot 0xd0fd6c76d7…74ddaf
Audit this contract →
← previous block·next block →recent activity