← previous blocknext block →recent activity
Analyzing
Block #95,810,949
21 transactions · 18 stateful · 2026-08-14 03:33:21 UTC
Parallelism
52/100
Blocked
50%
Avg conflicts / tx
2.14
Longest chain
10 deep
Execution timeline
did this block parallelize well?
view
block #95,810,949 · 21 txs across 10 waves · depth 10
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
wave w7
wave w8
wave w9
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
4w05w16w27w38w49w510w611w712w814w9
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x002fed35…79fa
0x2a68ba…90c5
18 touches
36 conflicts
0xa1087a5c…66c4
0x754704…b603
18 touches
36 conflicts
0x4febb4ad…04ee
0x065c9d…c394
17 touches
36 conflicts
0x595233b5…c4aa
0x754704…b603
4 touches
1 conflict
0x7e0b7922…c351
0x754704…b603
4 touches
1 conflict
0xa2478c84…6956
0x754704…b603
4 touches
1 conflict
0xf7adce63…0fd2
0x754704…b603
4 touches
1 conflict
0x0778475b…bd75
0x2a68ba…90c5
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
36 conflicts on slot 0x002fed350f…7379fa
Audit this contract →
← previous block·next block →recent activity