← previous blocknext block →recent activity
Analyzing
Block #82,221,286
14 transactions · 8 stateful · 2026-06-19 02:55:34 UTC
Parallelism
79/100
Blocked
38%
Avg conflicts / tx
0.21
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #82,221,286 · 14 txs across 3 waves · depth 3
parallel ↔ serial
wave w0
wave w1
wave w2
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w212w013w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…003d
0x065c9d…c394
4 touches
1 conflict
0x7ea6a117…f2f2
0x34b655…2a6f
4 touches
1 conflict
0xd98b3c10…67b8
0x34b655…2a6f
4 touches
1 conflict
0x23e155de…79ea
0xd32edf…ff58
3 touches
1 conflict
0x5540f956…69e8
0x065c9d…c394
2 touches
0 conflicts
0x57165ab1…56f1
0x065c9d…c394
2 touches
0 conflicts
0x57808eb5…9c03
0x065c9d…c394
2 touches
0 conflicts
0xa8c4d2b3…6a5c
0x065c9d…c394
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-MON/USDC
1 conflict on slot 0x0000000000…00003d
Audit this contract →
← previous block·next block →recent activity