← previous blocknext block →recent activity
Analyzing
Block #84,045,987
17 transactions · 15 stateful · 2026-06-27 14:00:30 UTC
Parallelism
82/100
Blocked
47%
Avg conflicts / tx
0.41
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #84,045,987 · 17 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
1w02w13w04w17w08w19w010w211w112w115w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x1d2a8430…30bf
0xa6afd3…d132
4 touches
1 conflict
0x3de5fb8b…400a
0xa6afd3…d132
4 touches
1 conflict
0x00000000…003d
0x065c9d…c394
4 touches
1 conflict
0x0b16149e…7d4d
0x065c9d…c394
4 touches
1 conflict
0x00000000…0012
0x1b6862…e19c
4 touches
1 conflict
0x00000000…0013
0x1b6862…e19c
4 touches
1 conflict
0x00000000…0015
0x1b6862…e19c
4 touches
1 conflict
0x00000000…001b
0x1b6862…e19c
4 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-WETH/USDC
1 conflict on slot 0x1d2a843070…4030bf
Audit this contract →
← previous block·next block →recent activity