← previous blocknext block →recent activity
Analyzing
Block #80,138,755
17 transactions · 10 stateful · 2026-06-09 11:33:39 UTC
Parallelism
76/100
Blocked
30%
Avg conflicts / tx
0.18
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #80,138,755 · 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
1w02w13w24w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x5540f956…69e8
0x065c9d…c394
4 touches
1 conflict
0x00000000…003d
0x065c9d…c394
4 touches
1 conflict
0xb182933f…46ed
0x754704…b603
2 touches
1 conflict
0x9d3f2124…725b
0x2a68ba…90c5
2 touches
1 conflict
0x5b571ba0…f13a
0x368ee5…7ca4
2 touches
0 conflicts
0x68faa0b9…14af
0x368ee5…7ca4
2 touches
0 conflicts
0xcd621226…2df8
0x368ee5…7ca4
2 touches
0 conflicts
0x354a0cfa…bcc7
0x754704…b603
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 0x5540f95607…2d69e8
Audit this contract →
← previous block·next block →recent activity