← previous blocknext block →recent activity
Analyzing
Block #80,230,942
17 transactions · 13 stateful · 2026-06-09 21:48:19 UTC
Parallelism
76/100
Blocked
23%
Avg conflicts / tx
0.35
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #80,230,942 · 17 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
1w02w03w04w15w26w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…003d
0x065c9d…c394
6 touches
3 conflicts
0x57ea9b78…fb22
0x065c9d…c394
4 touches
3 conflicts
0x21898044…a071
0x065c9d…c394
4 touches
1 conflict
0x13a54fa2…5ae3
0x2a68ba…90c5
4 touches
1 conflict
0x46c6a84f…1af8
0x065c9d…c394
3 touches
1 conflict
0x487d2922…28b6
0x754704…b603
2 touches
1 conflict
0xcb4ed39a…7d6d
0x065c9d…c394
2 touches
1 conflict
0x00000000…002f
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 0x0000000000…00003d
Audit this contract →
← previous block·next block →recent activity