← previous blocknext block →recent activity
Analyzing
Block #80,275,408
19 transactions · 15 stateful · 2026-06-10 02:44:55 UTC
Parallelism
79/100
Blocked
27%
Avg conflicts / tx
0.21
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #80,275,408 · 19 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
2w03w14w25w06w38w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…003d
0x065c9d…c394
4 touches
1 conflict
0xd821cffd…3ff0
0x754704…b603
4 touches
1 conflict
0x00000000…0008
0x86dbf0…eb2d
4 touches
1 conflict
0x61d65579…ee3c
0xad96c3…8d7c
4 touches
1 conflict
0x487d2922…28b6
0x754704…b603
2 touches
1 conflict
0x86e6cece…1fd5
0x2a68ba…90c5
2 touches
1 conflict
0x0bc20aba…027c
0x065c9d…c394
2 touches
0 conflicts
0xa228e10f…6356
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