← previous blocknext block →recent activity
Analyzing
Block #80,257,952
18 transactions · 13 stateful · 2026-06-10 00:48:30 UTC
Parallelism
67/100
Blocked
38%
Avg conflicts / tx
0.28
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #80,257,952 · 18 txs across 6 waves · depth 6
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w24w35w410w5
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x21898044…a071
0x065c9d…c394
4 touches
1 conflict
0x00000000…003d
0xa6afd3…d132
4 touches
1 conflict
0x179fe783…6945
0xa6afd3…d132
4 touches
1 conflict
0x13a54fa2…5ae3
0x2a68ba…90c5
4 touches
1 conflict
0x00000000…003d
0x065c9d…c394
4 touches
1 conflict
0x487d2922…28b6
0x754704…b603
2 touches
1 conflict
0x86e6cece…1fd5
0x2a68ba…90c5
2 touches
1 conflict
0x40970e69…da50
0x69df8a…6292
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 0x2189804463…a2a071
Audit this contract →
← previous block·next block →recent activity