← previous blocknext block →recent activity
Analyzing
Block #85,523,613
23 transactions · 16 stateful · 2026-07-04 10:09:37 UTC
Parallelism
83/100
Blocked
38%
Avg conflicts / tx
0.3
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #85,523,613 · 23 txs across 4 waves · depth 4
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
2w03w04w16w17w28w115w217w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…003d
0x065c9d…c394
6 touches
3 conflicts
0xb1f0701d…4f4a
0xc8689a…ee79
4 touches
1 conflict
0x13a54fa2…5ae3
0x2a68ba…90c5
4 touches
1 conflict
0x12530975…a089
0x3bd359…433a
4 touches
1 conflict
0x00000000…0000
0x453805…c7fd
4 touches
1 conflict
0x00000000…0002
0x453805…c7fd
4 touches
1 conflict
0x00000000…0004
0x453805…c7fd
4 touches
1 conflict
0x00000000…000c
0x453805…c7fd
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