← previous blocknext block →recent activity
Analyzing
Block #95,975,743
14 transactions · 13 stateful · 2026-08-14 17:22:36 UTC
Parallelism
71/100
Blocked
38%
Avg conflicts / tx
0.43
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #95,975,743 · 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
1w02w13w24w05w18w310w011w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x889d5e90…929a
0x2a68ba…90c5
6 touches
3 conflicts
0xf9137973…409f
0x968279…9342
4 touches
1 conflict
0xed101d7f…8ae5
0x968279…9342
4 touches
1 conflict
0xed101d7f…8ae7
0x968279…9342
4 touches
1 conflict
0xf9137973…4098
0x968279…9342
4 touches
1 conflict
0xf9137973…4099
0x968279…9342
4 touches
1 conflict
0xf9137973…409c
0x968279…9342
4 touches
1 conflict
0xf9137973…409d
0x968279…9342
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