← previous blocknext block →recent activity
Analyzing
Block #84,190,339
20 transactions · 18 stateful · 2026-06-28 06:01:40 UTC
Parallelism
65/100
Blocked
56%
Avg conflicts / tx
1.1
Longest chain
7 deep
Execution timeline
did this block parallelize well?
view
block #84,190,339 · 20 txs across 7 waves · depth 7
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w24w35w46w07w19w011w112w213w514w615w6
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…003d
0xa6afd3…d132
12 touches
15 conflicts
0x5da4ed2f…283f
0xa6afd3…d132
8 touches
6 conflicts
0xe99d8e68…a16e
0x34b655…2a6f
6 touches
3 conflicts
0xc05b880b…7746
0xa6afd3…d132
6 touches
3 conflicts
0xdf708ee7…1fcf
0xc8689a…ee79
6 touches
3 conflicts
0x13a54fa2…5ae3
0x2a68ba…90c5
6 touches
3 conflicts
0xd18a8dca…452f
0x1b6862…e19c
4 touches
1 conflict
0xd9f18d9a…141d
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
15 conflicts on slot 0x0000000000…00003d
Audit this contract →
← previous block·next block →recent activity