← previous blocknext block →recent activity
Analyzing
Block #85,619,954
11 transactions · 10 stateful · 2026-07-04 20:51:15 UTC
Parallelism
82/100
Blocked
20%
Avg conflicts / tx
0.18
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #85,619,954 · 11 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
1w02w14w07w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x37bf7688…12d7
0x065c9d…c394
4 touches
1 conflict
0x13a54fa2…5ae3
0x2a68ba…90c5
4 touches
1 conflict
0x00000000…003d
0x065c9d…c394
4 touches
1 conflict
0xb9cfad1d…1241
0x065c9d…c394
3 touches
1 conflict
0x00576fd3…d669
0x065c9d…c394
3 touches
1 conflict
0x17890cd9…736f
0x40c49f…2af0
2 touches
0 conflicts
0x6ad2d316…71e3
0x40c49f…2af0
2 touches
0 conflicts
0x74cd31bb…13d4
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 0x37bf76881c…d412d7
Audit this contract →
← previous block·next block →recent activity