← previous blocknext block →recent activity
Analyzing
Block #80,156,889
12 transactions · 11 stateful · 2026-06-09 13:34:28 UTC
Parallelism
75/100
Blocked
18%
Avg conflicts / tx
0.33
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #80,156,889 · 12 txs across 3 waves · depth 3
parallel ↔ serial
wave w0
wave w1
wave w2
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w03w04w15w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x5540f956…69e8
0x065c9d…c394
4 touches
1 conflict
0x13a54fa2…5ae3
0x2a68ba…90c5
4 touches
1 conflict
0x2425ecb4…da7d
0x065c9d…c394
3 touches
1 conflict
0x9a7e96d0…cfc7
0x065c9d…c394
3 touches
1 conflict
0x825f6ff3…2f4c
0xd32edf…ff58
3 touches
1 conflict
0x9ff176a9…152e
0x065c9d…c394
2 touches
0 conflicts
0xe4ce4757…3af7
0x065c9d…c394
2 touches
0 conflicts
0x09000000…0001
0x000000…1000
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