← previous blocknext block →recent activity
Analyzing
Block #82,426,590
30 transactions · 23 stateful · 2026-06-20 01:45:42 UTC
Parallelism
87/100
Blocked
52%
Avg conflicts / tx
0.7
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #82,426,590 · 30 txs across 4 waves · depth 4
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w04w05w16w17w28w39w010w118w019w120w223w324w326w329w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x66c5e348…51d0
0xa6afd3…d132
8 touches
6 conflicts
0xc824469a…6425
0x34b655…2a6f
6 touches
3 conflicts
0x482471ad…122f
0x34b655…2a6f
6 touches
3 conflicts
0x22d3c767…e4d1
0x34b655…2a6f
6 touches
3 conflicts
0x00000000…001b
0x1b6862…e19c
4 touches
1 conflict
0x00000000…002b
0x1b6862…e19c
4 touches
1 conflict
0xd9f18d9a…141d
0x1b6862…e19c
4 touches
1 conflict
0xed863ec8…90d9
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
6 conflicts on slot 0x66c5e3484c…3451d0
Audit this contract →
← previous block·next block →recent activity