← previous blocknext block →recent activity
Analyzing
Block #92,691,584
17 transactions · 15 stateful · 2026-08-03 05:30:02 UTC
Parallelism
88/100
Blocked
13%
Avg conflicts / tx
0.18
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #92,691,584 · 17 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
1w04w06w18w014w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x1c912a68…3b21
0x2a68ba…90c5
4 touches
1 conflict
0x77a99df7…d784
0x851145…3f07
4 touches
1 conflict
0x6ccf5c86…9954
0x851145…3f07
4 touches
1 conflict
0x36452290…362d
0x851145…3f07
4 touches
1 conflict
0x00000000…003d
0x851145…3f07
4 touches
1 conflict
0xda46a376…f6a6
0x34b655…2a6f
4 touches
1 conflict
0x1fd19887…8e0e
0x34b655…2a6f
4 touches
1 conflict
0x889d5e90…929a
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
1 conflict on slot 0x1c912a689a…d53b21
Audit this contract →
← previous block·next block →recent activity