← previous blocknext block →recent activity
Analyzing
Block #93,474,115
16 transactions · 15 stateful · 2026-08-05 23:07:27 UTC
Parallelism
88/100
Blocked
13%
Avg conflicts / tx
0.13
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #93,474,115 · 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
4w05w06w110w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…003d
0x065c9d…c394
4 touches
1 conflict
0xbcbf5d09…8bac
0x34b655…2a6f
4 touches
1 conflict
0xc824469a…6425
0x34b655…2a6f
4 touches
1 conflict
0x2794fd34…c82f
0x34b655…2a6f
2 touches
0 conflicts
0x2a2e70f3…3e00
0x34b655…2a6f
2 touches
0 conflicts
0x5a4cfbe3…8c5b
0x34b655…2a6f
2 touches
0 conflicts
0x76c4d722…afa9
0x34b655…2a6f
2 touches
0 conflicts
0x76c4d722…afaa
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: Market-MON/USDC
1 conflict on slot 0x0000000000…00003d
Audit this contract →
← previous block·next block →recent activity