← previous blocknext block →recent activity
Analyzing
Block #85,411,890
15 transactions · 13 stateful · 2026-07-03 21:45:49 UTC
Parallelism
80/100
Blocked
23%
Avg conflicts / tx
0.2
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #85,411,890 · 15 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
1w02w16w07w111w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x0f77bf68…c8db
0x065c9d…c394
4 touches
1 conflict
0x602dc3c2…cc24
0x065c9d…c394
4 touches
1 conflict
0x13a54fa2…5ae3
0x2a68ba…90c5
4 touches
1 conflict
0xfaef08b1…0696
0x34b655…2a6f
4 touches
1 conflict
0x00000000…003d
0x065c9d…c394
4 touches
1 conflict
0x09715d60…31f5
0x40c49f…2af0
2 touches
0 conflicts
0x2b33f092…45d2
0x40c49f…2af0
2 touches
0 conflicts
0xa2e7d991…c2df
0x40c49f…2af0
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 0x0f77bf689f…63c8db
Audit this contract →
← previous block·next block →recent activity