← previous blocknext block →recent activity
Analyzing
Block #80,493,080
11 transactions · 7 stateful · 2026-06-11 02:55:29 UTC
Parallelism
82/100
Blocked
14%
Avg conflicts / tx
0.09
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #80,493,080 · 11 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
2w07w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xb6b74ae0…8d5e
0xea1b8e…c5ec
4 touches
1 conflict
0x00bac013…a28c
0xfd44b3…00d1
4 touches
1 conflict
0x0b000000…0002
0x000000…1000
2 touches
0 conflicts
0x0e791fab…13e9
0x1efe02…37d6
2 touches
0 conflicts
0x0d622e34…0000
0x681e90…ae09
2 touches
0 conflicts
0x18adfb65…afc0
0xea1b8e…c5ec
2 touches
0 conflicts
0x455b104f…3960
0xea1b8e…c5ec
2 touches
0 conflicts
0xbc33a929…8b24
0xea1b8e…c5ec
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: LeverUp: LeverUp
1 conflict on slot 0xb6b74ae0ff…d48d5e
Audit this contract →
← previous block·next block →recent activity