← previous blocknext block →recent activity
Analyzing
Block #95,180,776
13 transactions · 12 stateful · 2026-08-11 22:29:07 UTC
Parallelism
54/100
Blocked
50%
Avg conflicts / tx
1.23
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #95,180,776 · 13 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
2w04w15w06w17w28w39w410w5
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x382e6cdf…7286
0x40c49f…2af0
12 touches
15 conflicts
0x2b54cadb…4425
0xd18b7e…414b
12 touches
15 conflicts
0xa1087a5c…66c4
0x754704…b603
12 touches
15 conflicts
0x002fed35…79fa
0x2a68ba…90c5
12 touches
15 conflicts
0x52037bd1…2ad8
0xd18b7e…414b
4 touches
1 conflict
0x22e0cc1d…ad0d
0x34b655…2a6f
4 touches
1 conflict
0x595233b5…c4aa
0x754704…b603
4 touches
1 conflict
0x91eb94de…b47b
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: 0x40c49f17…d22af0
15 conflicts on slot 0x382e6cdf15…067286
Audit this contract →
← previous block·next block →recent activity