← previous blocknext block →recent activity
Analyzing
Block #90,822,333
11 transactions · 9 stateful · 2026-07-27 16:43:14 UTC
Parallelism
82/100
Blocked
22%
Avg conflicts / tx
0.18
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #90,822,333 · 11 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
1w02w19w010w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x9ff176a9…152e
0x065c9d…c394
4 touches
1 conflict
0x00000000…003d
0x065c9d…c394
4 touches
1 conflict
0x5540f956…69e8
0x065c9d…c394
4 touches
1 conflict
0x0b751c51…93e9
0x34b655…2a6f
4 touches
1 conflict
0x3a51d8ed…0c97
0x34b655…2a6f
4 touches
1 conflict
0x6ec11f62…98a6
0x34b655…2a6f
4 touches
1 conflict
0xb1912676…a60c
0x34b655…2a6f
4 touches
1 conflict
0xb3950136…8e7d
0x34b655…2a6f
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: Market-MON/USDC
1 conflict on slot 0x9ff176a9ad…67152e
Audit this contract →
← previous block·next block →recent activity