← previous blocknext block →recent activity
Analyzing
Block #96,113,018
28 transactions · 20 stateful · 2026-08-15 04:53:11 UTC
Parallelism
82/100
Blocked
40%
Avg conflicts / tx
0.46
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #96,113,018 · 28 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
8w09w110w211w319w021w122w023w124w225w426w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x889d5e90…929a
0x2a68ba…90c5
8 touches
6 conflicts
0x3988e089…753c
0x968279…9342
6 touches
3 conflicts
0x26812576…4678
0x968279…9342
6 touches
3 conflicts
0x26812576…4679
0x968279…9342
6 touches
3 conflicts
0x26812576…467c
0x968279…9342
6 touches
3 conflicts
0x26812576…467d
0x968279…9342
6 touches
3 conflicts
0x26812576…467f
0x968279…9342
6 touches
3 conflicts
0x3988e089…7539
0x968279…9342
6 touches
3 conflicts
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
6 conflicts on slot 0x889d5e90c7…59929a
Audit this contract →
← previous block·next block →recent activity