← previous blocknext block →recent activity
Analyzing
Block #85,175,408
13 transactions · 12 stateful · 2026-07-02 19:30:39 UTC
Parallelism
62/100
Blocked
50%
Avg conflicts / tx
0.69
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #85,175,408 · 13 txs across 5 waves · depth 5
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
2w03w04w16w28w39w411w112w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…003d
0x065c9d…c394
6 touches
3 conflicts
0x002fed35…79fa
0x2a68ba…90c5
6 touches
3 conflicts
0xa973245e…0175
0x065c9d…c394
5 touches
3 conflicts
0xf76fd3e7…53cc
0x754704…b603
4 touches
1 conflict
0x731e6d82…2883
0x065c9d…c394
4 touches
1 conflict
0x43e2eda1…396f
0x34b655…2a6f
4 touches
1 conflict
0xceb535f3…19cf
0x34b655…2a6f
4 touches
1 conflict
0xd98b3c10…67b8
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
3 conflicts on slot 0x0000000000…00003d
Audit this contract →
← previous block·next block →recent activity