← previous blocknext block →recent activity
Analyzing
Block #90,330,307
9 transactions · 9 stateful · 2026-07-25 23:16:19 UTC
Parallelism
78/100
Blocked
22%
Avg conflicts / tx
0.22
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #90,330,307 · 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
3w05w06w17w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…003d
0x065c9d…c394
4 touches
1 conflict
0x41f1e2e5…2edf
0x34b655…2a6f
4 touches
1 conflict
0x4de96d1d…b043
0x34b655…2a6f
4 touches
1 conflict
0x017cb6f4…0329
0x34b655…2a6f
2 touches
0 conflicts
0x044c16fd…5d78
0x34b655…2a6f
2 touches
0 conflicts
0x0a6e8942…fd6a
0x34b655…2a6f
2 touches
0 conflicts
0x0a6e8942…fd6b
0x34b655…2a6f
2 touches
0 conflicts
0x0aa5e418…5d1d
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