← previous blocknext block →recent activity
Analyzing
Block #95,277,299
14 transactions · 14 stateful · 2026-08-12 06:43:30 UTC
Parallelism
71/100
Blocked
29%
Avg conflicts / tx
0.5
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #95,277,299 · 14 txs across 4 waves · depth 4
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
3w04w15w26w312w013w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xa4eb4abf…54e5
0x40c49f…2af0
8 touches
6 conflicts
0x002fed35…79fa
0x2a68ba…90c5
8 touches
6 conflicts
0x2b54cadb…4425
0xd18b7e…414b
8 touches
6 conflicts
0xa1087a5c…66c4
0x754704…b603
8 touches
6 conflicts
0x595233b5…c4aa
0x754704…b603
4 touches
1 conflict
0x91eb94de…b47b
0x754704…b603
4 touches
1 conflict
0x4df2af73…275a
0xd18b7e…414b
4 touches
1 conflict
0x0d2de0f6…e6c6
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: 0x40c49f17…d22af0
6 conflicts on slot 0xa4eb4abf88…ae54e5
Audit this contract →
← previous block·next block →recent activity