← previous blocknext block →recent activity
Analyzing
Block #93,200,117
16 transactions · 15 stateful · 2026-08-05 00:09:53 UTC
Parallelism
88/100
Blocked
7%
Avg conflicts / tx
0.13
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #93,200,117 · 16 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
1w04w05w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x889d5e90…929a
0x2a68ba…90c5
4 touches
1 conflict
0x00000000…003d
0x065c9d…c394
4 touches
1 conflict
0x9ff176a9…152e
0x065c9d…c394
4 touches
1 conflict
0x0caf97ee…c90a
0x065c9d…c394
2 touches
0 conflicts
0x1621230b…a11d
0x065c9d…c394
2 touches
0 conflicts
0x601833c3…458b
0x065c9d…c394
2 touches
0 conflicts
0x685e4d68…48da
0x065c9d…c394
2 touches
0 conflicts
0xa913bb38…240d
0x065c9d…c394
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 0x889d5e90c7…59929a
Audit this contract →
← previous block·next block →recent activity