← previous blocknext block →recent activity
Analyzing
Block #85,853,954
20 transactions · 11 stateful · 2026-07-05 22:50:45 UTC
Parallelism
90/100
Blocked
18%
Avg conflicts / tx
0.1
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #85,853,954 · 20 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
3w04w117w018w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x513e200b…e0a1
0x065c9d…c394
4 touches
1 conflict
0xd98b3c10…67b8
0x34b655…2a6f
4 touches
1 conflict
0x21898044…a071
0x065c9d…c394
4 touches
1 conflict
0x00000000…003d
0x065c9d…c394
4 touches
1 conflict
0xff4bbb6b…b25f
0x065c9d…c394
4 touches
1 conflict
0x01a88dca…3bdf
0x065c9d…c394
3 touches
1 conflict
0x4d61d584…70c0
0x065c9d…c394
3 touches
1 conflict
0x7aad02c6…b979
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 0x513e200be9…75e0a1
Audit this contract →
← previous block·next block →recent activity