← previous blocknext block →recent activity
Analyzing
Block #86,698,394
10 transactions · 9 stateful · 2026-07-09 20:52:01 UTC
Parallelism
80/100
Blocked
22%
Avg conflicts / tx
0.2
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #86,698,394 · 10 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
1w04w15w09w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x909e34a2…ba7c
0x065c9d…c394
4 touches
1 conflict
0xea47653c…b9ad
0x065c9d…c394
4 touches
1 conflict
0x00000000…003d
0x065c9d…c394
4 touches
1 conflict
0x9fd372a1…a959
0x34b655…2a6f
4 touches
1 conflict
0x514a2979…93ca
0x065c9d…c394
3 touches
1 conflict
0x58b4c3fc…e0d8
0x065c9d…c394
3 touches
1 conflict
0x667555fa…b7ad
0x065c9d…c394
3 touches
1 conflict
0xe78ecaba…a982
0x065c9d…c394
3 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 0x909e34a281…acba7c
Audit this contract →
← previous block·next block →recent activity