← previous blocknext block →recent activity
Analyzing
Block #83,762,648
20 transactions · 19 stateful · 2026-06-26 06:31:22 UTC
Parallelism
80/100
Blocked
42%
Avg conflicts / tx
0.6
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #83,762,648 · 20 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
1w02w03w14w05w16w07w18w29w311w212w014w117w018w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x7263b4fb…09dc
0xa6afd3…d132
6 touches
3 conflicts
0x00000000…003d
0xa6afd3…d132
6 touches
3 conflicts
0xf2f76ab3…623e
0x2a68ba…90c5
4 touches
1 conflict
0x0eac6378…36f4
0x34b655…2a6f
4 touches
1 conflict
0x226b141d…1864
0x34b655…2a6f
4 touches
1 conflict
0x53b4ef2b…8a05
0x34b655…2a6f
4 touches
1 conflict
0x737acb78…fce8
0x34b655…2a6f
4 touches
1 conflict
0xab86573c…682e
0x34b655…2a6f
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