← previous blocknext block →recent activity
Analyzing
Block #93,666,619
9 transactions · 8 stateful · 2026-08-06 15:15:11 UTC
Parallelism
78/100
Blocked
38%
Avg conflicts / tx
0.33
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #93,666,619 · 9 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
1w02w03w14w15w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xc3edbf08…6ce8
0x065c9d…c394
4 touches
1 conflict
0x883e9a5b…0f01
0x34b655…2a6f
4 touches
1 conflict
0x898d9b8a…d1ef
0x34b655…2a6f
4 touches
1 conflict
0x1e56f6b6…5940
0x34b655…2a6f
4 touches
1 conflict
0xe88fde4c…f3b1
0x065c9d…c394
3 touches
1 conflict
0xf899fe5c…b233
0x065c9d…c394
3 touches
1 conflict
0x889d5e90…929a
0x2a68ba…90c5
2 touches
0 conflicts
0x06e40499…165e
0x2b46c0…1669
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 0xc3edbf084e…516ce8
Audit this contract →
← previous block·next block →recent activity