← previous blocknext block →recent activity
Analyzing
Block #84,332,684
20 transactions · 16 stateful · 2026-06-28 21:50:12 UTC
Parallelism
90/100
Blocked
6%
Avg conflicts / tx
0.1
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #84,332,684 · 20 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
15w016w017w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x975680c7…0e39
0xa6afd3…d132
4 touches
1 conflict
0xb3572c95…9c4a
0x2a68ba…90c5
4 touches
1 conflict
0x00000000…003d
0xa6afd3…d132
4 touches
1 conflict
0x38aa1898…fdf5
0x11ed3b…2c96
2 touches
0 conflicts
0x39b87ad0…9fd7
0x11ed3b…2c96
2 touches
0 conflicts
0x3e98e7ac…698b
0x188d58…ea8e
2 touches
0 conflicts
0x3e98e7ac…698d
0x188d58…ea8e
2 touches
0 conflicts
0x40e2d65d…2a35
0x3bd359…433a
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 0x975680c7cb…460e39
Audit this contract →
← previous block·next block →recent activity