← previous blocknext block →recent activity
Analyzing
Block #86,244,858
18 transactions · 15 stateful · 2026-07-07 18:19:15 UTC
Parallelism
83/100
Blocked
20%
Avg conflicts / tx
0.22
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #86,244,858 · 18 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
2w010w111w213w014w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…003d
0x065c9d…c394
6 touches
3 conflicts
0x1e9a8e72…7138
0x43cf54…7777
4 touches
1 conflict
0xdfa159d0…1576
0x065c9d…c394
4 touches
1 conflict
0xd61a7c18…9f3e
0x065c9d…c394
3 touches
1 conflict
0xcc4f1f14…aa5f
0x065c9d…c394
2 touches
0 conflicts
0x13a54fa2…5ae3
0x2a68ba…90c5
2 touches
0 conflicts
0x7d42dc8b…fdb6
0x2a68ba…90c5
2 touches
0 conflicts
0x9ff4ca89…6115
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
3 conflicts on slot 0x0000000000…00003d
Audit this contract →
← previous block·next block →recent activity