← previous blocknext block →recent activity
Analyzing
Block #80,292,476
9 transactions · 8 stateful · 2026-06-10 04:38:42 UTC
Parallelism
78/100
Blocked
25%
Avg conflicts / tx
0.22
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #80,292,476 · 9 txs across 2 waves · depth 2
parallel ↔ serial
wave w0
wave w1
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…003d
0x065c9d…c394
4 touches
1 conflict
0x5540f956…69e8
0x065c9d…c394
4 touches
1 conflict
0x34082b91…5f27
0x065c9d…c394
2 touches
0 conflicts
0x49898b74…8f5d
0x065c9d…c394
2 touches
0 conflicts
0x898ed679…9643
0x065c9d…c394
2 touches
0 conflicts
0x9f97d127…a8de
0x065c9d…c394
2 touches
0 conflicts
0xae222fa7…4e13
0x065c9d…c394
2 touches
0 conflicts
0xf379a44b…38d1
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