← previous blocknext block →recent activity
Analyzing
Block #85,254,002
12 transactions · 11 stateful · 2026-07-03 04:14:16 UTC
Parallelism
83/100
Blocked
18%
Avg conflicts / tx
0.17
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #85,254,002 · 12 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
2w04w05w16w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xf6fb9ed4…f0b9
0x065c9d…c394
4 touches
1 conflict
0x9cf2d0bf…8d46
0x34b655…2a6f
4 touches
1 conflict
0xe5bb3628…e5f1
0x34b655…2a6f
4 touches
1 conflict
0x00000000…003d
0x065c9d…c394
4 touches
1 conflict
0x61bc9569…4823
0x065c9d…c394
4 touches
1 conflict
0x7ccc375a…26b0
0x34b655…2a6f
4 touches
1 conflict
0x061f9381…a10b
0x34b655…2a6f
2 touches
0 conflicts
0x1e7e4246…4872
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 0xf6fb9ed45e…6cf0b9
Audit this contract →
← previous block·next block →recent activity