← previous blocknext block →recent activity
Analyzing
Block #84,357,492
22 transactions · 18 stateful · 2026-06-29 00:35:34 UTC
Parallelism
77/100
Blocked
44%
Avg conflicts / tx
0.55
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #84,357,492 · 22 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
1w02w14w05w111w014w215w216w317w420w121w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x7263b4fb…09dc
0xa6afd3…d132
6 touches
3 conflicts
0xea02471d…1542
0x34b655…2a6f
6 touches
3 conflicts
0x00000000…003d
0xa6afd3…d132
6 touches
3 conflicts
0x00000000…0013
0x1b6862…e19c
4 touches
1 conflict
0x00000000…0015
0x1b6862…e19c
4 touches
1 conflict
0x00000000…001a
0x1b6862…e19c
4 touches
1 conflict
0x00000000…002a
0x1b6862…e19c
4 touches
1 conflict
0xba5743c7…21c1
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 0x7263b4fb47…e309dc
Audit this contract →
← previous block·next block →recent activity