← previous blocknext block →recent activity
Analyzing
Block #93,675,045
23 transactions · 20 stateful · 2026-08-06 15:57:32 UTC
Parallelism
83/100
Blocked
60%
Avg conflicts / tx
0.87
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #93,675,045 · 23 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
1w02w13w26w07w18w110w111w212w213w314w116w217w221w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x889d5e90…929a
0x2a68ba…90c5
8 touches
6 conflicts
0xc6b9bb4b…145a
0x34b655…2a6f
6 touches
3 conflicts
0x00000000…003d
0x40c49f…2af0
6 touches
3 conflicts
0xf8e5c38f…a6ee
0xd32edf…ff58
5 touches
3 conflicts
0x00000000…002c
0x1b6862…e19c
4 touches
1 conflict
0x6b1259e6…4e11
0x1b6862…e19c
4 touches
1 conflict
0xd9f18d9a…141d
0x1b6862…e19c
4 touches
1 conflict
0xaeb5864c…7679
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
6 conflicts on slot 0x889d5e90c7…59929a
Audit this contract →
← previous block·next block →recent activity