← previous blocknext block →recent activity
Analyzing
Block #85,639,830
11 transactions · 11 stateful · 2026-07-04 23:03:24 UTC
Parallelism
73/100
Blocked
27%
Avg conflicts / tx
0.36
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #85,639,830 · 11 txs across 3 waves · depth 3
parallel ↔ serial
wave w0
wave w1
wave w2
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w04w15w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x5540f956…69e8
0x065c9d…c394
6 touches
3 conflicts
0x00000000…003d
0x065c9d…c394
6 touches
3 conflicts
0x13a54fa2…5ae3
0x2a68ba…90c5
4 touches
1 conflict
0x0c7672e2…c51c
0x065c9d…c394
3 touches
1 conflict
0xf379a44b…38d1
0x065c9d…c394
3 touches
1 conflict
0xf30d4f9c…cbe4
0x065c9d…c394
3 touches
1 conflict
0x1ea5f265…0d61
0x065c9d…c394
3 touches
1 conflict
0xc4c192ab…2de8
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
3 conflicts on slot 0x5540f95607…2d69e8
Audit this contract →
← previous block·next block →recent activity