← previous blocknext block →recent activity
Analyzing
Block #95,202,346
16 transactions · 16 stateful · 2026-08-12 00:17:36 UTC
Parallelism
69/100
Blocked
31%
Avg conflicts / tx
0.44
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #95,202,346 · 16 txs across 5 waves · depth 5
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w04w19w210w311w414w015w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x002fed35…79fa
0x2a68ba…90c5
6 touches
3 conflicts
0xa1087a5c…66c4
0x754704…b603
6 touches
3 conflicts
0x8f0d6dda…e052
0x40c49f…2af0
5 touches
3 conflicts
0x0444cd83…8f27
0x754704…b603
4 touches
1 conflict
0x4df2af73…275a
0xd18b7e…414b
4 touches
1 conflict
0xa2478c84…6956
0x754704…b603
4 touches
1 conflict
0xc799e56d…45aa
0x34b655…2a6f
4 touches
1 conflict
0x2b54cadb…4425
0xd18b7e…414b
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: Kuru Exchange: MarginAccount
3 conflicts on slot 0x002fed350f…7379fa
Audit this contract →
← previous block·next block →recent activity