← previous blocknext block →recent activity
Analyzing
Block #86,044,893
14 transactions · 10 stateful · 2026-07-06 20:04:35 UTC
Parallelism
79/100
Blocked
20%
Avg conflicts / tx
0.21
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #86,044,893 · 14 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
1w010w111w2
- 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
4 touches
1 conflict
0xbdfb7631…e6c6
0x065c9d…c394
3 touches
1 conflict
0x11140442…62cb
0x065c9d…c394
2 touches
0 conflicts
0x2400ca14…3495
0x065c9d…c394
2 touches
0 conflicts
0x49cbdb1b…bda4
0x065c9d…c394
2 touches
0 conflicts
0x52126642…95f2
0x065c9d…c394
2 touches
0 conflicts
0xba36d6bc…a7df
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