← previous blocknext block →recent activity
Analyzing
Block #85,413,315
8 transactions · 7 stateful · 2026-07-03 21:55:21 UTC
Parallelism
75/100
Blocked
29%
Avg conflicts / tx
0.25
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #85,413,315 · 8 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
1w02w16w07w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x5540f956…69e8
0x065c9d…c394
4 touches
1 conflict
0xd98b3c10…67b8
0x34b655…2a6f
4 touches
1 conflict
0x00000000…003d
0x065c9d…c394
4 touches
1 conflict
0x18cd5e3f…70c9
0x065c9d…c394
2 touches
0 conflicts
0x744e71d6…becb
0x065c9d…c394
2 touches
0 conflicts
0x7db2a5e6…b40c
0x065c9d…c394
2 touches
0 conflicts
0xa4564575…389e
0x065c9d…c394
2 touches
0 conflicts
0xcd642400…9b0a
0x065c9d…c394
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 0x5540f95607…2d69e8
Audit this contract →
← previous block·next block →recent activity