← previous blocknext block →recent activity
Analyzing
Block #80,310,300
14 transactions · 12 stateful · 2026-06-10 06:37:31 UTC
Parallelism
79/100
Blocked
42%
Avg conflicts / tx
0.5
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #80,310,300 · 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
1w02w13w14w07w212w113w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x80afd9d9…57cf
0x065c9d…c394
6 touches
3 conflicts
0xb4e0a934…5fc7
0x34b655…2a6f
6 touches
3 conflicts
0x5e923109…b38e
0x065c9d…c394
4 touches
2 conflicts
0x00000000…003d
0x065c9d…c394
4 touches
1 conflict
0xd98b3c10…67b8
0x34b655…2a6f
4 touches
1 conflict
0x4bf20b96…cbfb
0x065c9d…c394
3 touches
1 conflict
0x35739fcf…7030
0x065c9d…c394
3 touches
1 conflict
0x00000000…0019
0x1b6862…e19c
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
3 conflicts on slot 0x80afd9d9f2…3f57cf
Audit this contract →
← previous block·next block →recent activity