← previous blocknext block →recent activity
Analyzing
Block #93,500,997
16 transactions · 14 stateful · 2026-08-06 01:22:36 UTC
Parallelism
75/100
Blocked
43%
Avg conflicts / tx
0.63
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #93,500,997 · 16 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
1w03w05w07w18w29w311w112w114w015w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x002fed35…79fa
0x2a68ba…90c5
8 touches
6 conflicts
0xa1087a5c…66c4
0x754704…b603
6 touches
3 conflicts
0x52037bd1…2ad8
0xd18b7e…414b
4 touches
1 conflict
0x00000000…004c
0x80c745…7210
4 touches
1 conflict
0x00000000…003d
0x851145…3f07
4 touches
1 conflict
0xcfeed415…e4ab
0x851145…3f07
4 touches
1 conflict
0xe47f0750…4816
0x851145…3f07
4 touches
1 conflict
0x2b54cadb…4425
0xd18b7e…414b
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
6 conflicts on slot 0x002fed350f…7379fa
Audit this contract →
← previous block·next block →recent activity