← previous blocknext block →recent activity
Analyzing
Block #84,404,261
11 transactions · 10 stateful · 2026-06-29 05:47:23 UTC
Parallelism
82/100
Blocked
10%
Avg conflicts / tx
0.09
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #84,404,261 · 11 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
1w010w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x5deb8dbd…b994
0xa6afd3…d132
4 touches
1 conflict
0x11b69a7e…334e
0xee8c0e…1242
4 touches
1 conflict
0xa1087a5c…66c4
0x754704…b603
4 touches
1 conflict
0xef65bff3…7c9d
0x2a68ba…90c5
4 touches
1 conflict
0x729c91b8…9538
0x188d58…ea8e
2 touches
0 conflicts
0x01a89030…f786
0x368ee5…7ca4
2 touches
0 conflicts
0x17606ba6…1b6e
0x754704…b603
2 touches
0 conflicts
0x01a89030…f786
0x98dc6e…8633
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 0x5deb8dbd8c…f6b994
Audit this contract →
← previous block·next block →recent activity