← previous blocknext block →recent activity
Analyzing
Block #86,922,288
9 transactions · 9 stateful · 2026-07-10 21:48:22 UTC
Parallelism
78/100
Blocked
11%
Avg conflicts / tx
0.11
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #86,922,288 · 9 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
1w05w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xa4f80979…4d71
0x065c9d…c394
4 touches
1 conflict
0xd35bb5ac…3586
0x065c9d…c394
4 touches
1 conflict
0x00000000…003d
0x065c9d…c394
4 touches
1 conflict
0x1ad5ea15…c63c
0x065c9d…c394
3 touches
1 conflict
0x8a8950d7…fa94
0x065c9d…c394
2 touches
0 conflicts
0x96f0e7c7…70d7
0x065c9d…c394
2 touches
0 conflicts
0xa0bdc782…cb62
0x065c9d…c394
2 touches
0 conflicts
0xf61184f4…1676
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 0xa4f8097941…fd4d71
Audit this contract →
← previous block·next block →recent activity