← previous blocknext block →recent activity
Analyzing
Block #95,744,335
10 transactions · 9 stateful · 2026-08-13 21:58:20 UTC
Parallelism
70/100
Blocked
33%
Avg conflicts / tx
0.4
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #95,744,335 · 10 txs across 3 waves · depth 3
parallel ↔ serial
wave w0
wave w1
wave w2
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w06w17w28w09w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x0778475b…bd75
0x2a68ba…90c5
6 touches
3 conflicts
0x04cca030…07b9
0x065c9d…c394
5 touches
3 conflicts
0x09106a95…1467
0x33176b…e078
4 touches
1 conflict
0x00000000…003d
0x065c9d…c394
4 touches
1 conflict
0x1eb432b0…79a4
0x065c9d…c394
4 touches
1 conflict
0xb0f6539b…8067
0x065c9d…c394
4 touches
1 conflict
0xeb5bb0ab…edb7
0x065c9d…c394
3 touches
1 conflict
0x4e228584…1dfe
0x065c9d…c394
3 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 0x0778475bb2…63bd75
Audit this contract →
← previous block·next block →recent activity