← previous blocknext block →recent activity
Analyzing
Block #84,360,164
14 transactions · 14 stateful · 2026-06-29 00:53:27 UTC
Parallelism
86/100
Blocked
7%
Avg conflicts / tx
0.07
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #84,360,164 · 14 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
1w011w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x3287e4ec…eaa3
0xa6afd3…d132
4 touches
1 conflict
0x774f6545…8d8c
0xa6afd3…d132
3 touches
1 conflict
0xaab8b8e3…fab1
0xa6afd3…d132
3 touches
1 conflict
0x13a54fa2…5ae3
0x2a68ba…90c5
2 touches
0 conflicts
0xc08384da…ecb7
0x34b655…2a6f
2 touches
0 conflicts
0xd33e70b0…1515
0x34b655…2a6f
2 touches
0 conflicts
0xe99d8e68…a16e
0x34b655…2a6f
2 touches
0 conflicts
0x40970e69…da50
0x69df8a…6292
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-WETH/USDC
1 conflict on slot 0x3287e4ecfd…5aeaa3
Audit this contract →
← previous block·next block →recent activity