← previous blocknext block →recent activity
Analyzing
Block #80,743,858
19 transactions · 15 stateful · 2026-06-12 06:48:37 UTC
Parallelism
74/100
Blocked
40%
Avg conflicts / tx
0.47
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #80,743,858 · 19 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
1w03w14w25w37w311w012w113w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…003d
0x065c9d…c394
8 touches
6 conflicts
0x80afd9d9…57cf
0x065c9d…c394
8 touches
6 conflicts
0xac0f2a19…d2e0
0x34b655…2a6f
4 touches
1 conflict
0xc8a10d9e…919f
0x34b655…2a6f
4 touches
1 conflict
0xff8759c6…784b
0x34b655…2a6f
4 touches
1 conflict
0x00000000…003d
0xa6afd3…d132
4 touches
1 conflict
0x52d65d97…1c96
0xa6afd3…d132
4 touches
1 conflict
0x2e4eea52…0c68
0xc8689a…ee79
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-MON/USDC
6 conflicts on slot 0x0000000000…00003d
Audit this contract →
← previous block·next block →recent activity