← previous blocknext block →recent activity
Analyzing
Block #95,424,175
24 transactions · 21 stateful · 2026-08-12 19:06:56 UTC
Parallelism
67/100
Blocked
48%
Avg conflicts / tx
0.96
Longest chain
8 deep
Execution timeline
did this block parallelize well?
view
block #95,424,175 · 24 txs across 8 waves · depth 8
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
wave w7
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
2w03w14w25w26w37w48w510w315w622w523w7
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x734ee320…caae
0x34b655…2a6f
12 touches
15 conflicts
0x8109fc8f…5ce3
0x34b655…2a6f
6 touches
3 conflicts
0xe9452241…95a3
0x34b655…2a6f
6 touches
3 conflicts
0xec7d120d…7084
0x34b655…2a6f
6 touches
3 conflicts
0x52f3d91c…1822
0x34b655…2a6f
4 touches
1 conflict
0x7523c6af…ea66
0x34b655…2a6f
4 touches
1 conflict
0x7e5ea60a…c4aa
0x34b655…2a6f
4 touches
1 conflict
0x823a3658…acf6
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
15 conflicts on slot 0x734ee32053…cecaae
Audit this contract →
← previous block·next block →recent activity