← previous blocknext block →recent activity
Analyzing
Block #86,362,689
30 transactions · 24 stateful · 2026-07-08 07:25:59 UTC
Parallelism
87/100
Blocked
21%
Avg conflicts / tx
0.27
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #86,362,689 · 30 txs across 4 waves · depth 4
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w15w06w110w017w219w120w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…003d
0x065c9d…c394
6 touches
3 conflicts
0x27a04273…27c5
0x065c9d…c394
6 touches
3 conflicts
0x63cd7ec7…1641
0xd32edf…ff58
5 touches
3 conflicts
0xdd70bea3…1ffe
0x3bd359…433a
4 touches
1 conflict
0x62470977…f5da
0x065c9d…c394
4 touches
1 conflict
0xba1db0c8…3b89
0x065c9d…c394
3 touches
1 conflict
0xc5637347…cc41
0x065c9d…c394
3 touches
1 conflict
0x99b05853…d3b2
0x065c9d…c394
3 touches
1 conflict
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