← previous blocknext block →recent activity
Analyzing
Block #95,243,030
20 transactions · 18 stateful · 2026-08-12 03:42:14 UTC
Parallelism
75/100
Blocked
33%
Avg conflicts / tx
0.35
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #95,243,030 · 20 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
2w03w14w28w39w311w012w118w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x889d5e90…929a
0x2a68ba…90c5
6 touches
3 conflicts
0xa4e35471…d368
0x968279…9342
4 touches
1 conflict
0x66a71aa9…29e7
0x968279…9342
4 touches
1 conflict
0x66a71aa9…29e9
0x968279…9342
4 touches
1 conflict
0xa4e35471…d363
0x968279…9342
4 touches
1 conflict
0xa4e35471…d364
0x968279…9342
4 touches
1 conflict
0xa4e35471…d367
0x968279…9342
4 touches
1 conflict
0x002fed35…79fa
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
3 conflicts on slot 0x889d5e90c7…59929a
Audit this contract →
← previous block·next block →recent activity