← previous blocknext block →recent activity
Analyzing
Block #84,248,422
27 transactions · 25 stateful · 2026-06-28 12:28:49 UTC
Parallelism
81/100
Blocked
36%
Avg conflicts / tx
0.44
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #84,248,422 · 27 txs across 5 waves · depth 5
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
2w08w09w111w012w113w114w216w217w221w322w425w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x2d5c395b…6b5a
0xa6afd3…d132
6 touches
3 conflicts
0x7c5260f4…bd96
0xa6afd3…d132
6 touches
3 conflicts
0xf2f76ab3…623e
0x2a68ba…90c5
6 touches
3 conflicts
0x00000000…001f
0x1b6862…e19c
4 touches
1 conflict
0x00000000…002f
0x1b6862…e19c
4 touches
1 conflict
0x013bb37b…eb50
0x1b6862…e19c
4 touches
1 conflict
0xd9f18d9a…141d
0x1b6862…e19c
4 touches
1 conflict
0x00000000…0012
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
3 conflicts on slot 0x2d5c395b26…9d6b5a
Audit this contract →
← previous block·next block →recent activity