← previous blocknext block →recent activity
Analyzing
Block #93,676,696
11 transactions · 9 stateful · 2026-08-06 16:05:50 UTC
Parallelism
82/100
Blocked
22%
Avg conflicts / tx
0.18
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #93,676,696 · 11 txs across 2 waves · depth 2
parallel ↔ serial
wave w0
wave w1
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
2w03w05w17w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xaeb5864c…7679
0x2a68ba…90c5
4 touches
1 conflict
0x4e58f1d6…2fca
0x34b655…2a6f
4 touches
1 conflict
0x482471ad…122f
0x34b655…2a6f
4 touches
1 conflict
0x39b94f64…8e0e
0x40c49f…2af0
3 touches
1 conflict
0x0179e71d…e168
0x34b655…2a6f
2 touches
0 conflicts
0x071ff290…ec09
0x34b655…2a6f
2 touches
0 conflicts
0x0933b65e…e7d4
0x34b655…2a6f
2 touches
0 conflicts
0x11db128b…1153
0x34b655…2a6f
2 touches
0 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
1 conflict on slot 0xaeb5864c20…607679
Audit this contract →
← previous block·next block →recent activity