← previous blocknext block →recent activity
Analyzing
Block #86,151,494
10 transactions · 8 stateful · 2026-07-07 07:55:49 UTC
Parallelism
70/100
Blocked
25%
Avg conflicts / tx
0.3
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #86,151,494 · 10 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
1w02w16w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…003d
0x065c9d…c394
6 touches
3 conflicts
0x77ed432f…fa04
0x065c9d…c394
4 touches
1 conflict
0x89a703a1…a119
0x065c9d…c394
3 touches
1 conflict
0x23f2f337…4cb6
0x065c9d…c394
2 touches
0 conflicts
0x5ec6dabe…a73c
0x065c9d…c394
2 touches
0 conflicts
0x8a46802c…fe1c
0x065c9d…c394
2 touches
0 conflicts
0xaf5222e2…2f4f
0x065c9d…c394
2 touches
0 conflicts
0xb6c76c66…1848
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
3 conflicts on slot 0x0000000000…00003d
Audit this contract →
← previous block·next block →recent activity