← previous blocknext block →recent activity
Analyzing
Block #80,549,940
18 transactions · 17 stateful · 2026-06-11 09:14:15 UTC
Parallelism
50/100
Blocked
47%
Avg conflicts / tx
2
Longest chain
9 deep
Execution timeline
did this block parallelize well?
view
block #80,549,940 · 18 txs across 9 waves · depth 9
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
wave w7
wave w8
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
5w06w17w28w39w410w511w612w713w8
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…0003
0xf96746…f1db
17 touches
36 conflicts
0x09000000…0007
0x000000…1000
2 touches
0 conflicts
0x00000000…006f
0x1efe02…37d6
2 touches
0 conflicts
0x1f9e288c…b001
0x1efe02…37d6
2 touches
0 conflicts
0x85f24ee5…d2c2
0x1efe02…37d6
2 touches
0 conflicts
0xbbf98631…ca11
0x1efe02…37d6
2 touches
0 conflicts
0x00000000…0099
0xaa3145…feec
2 touches
0 conflicts
0x593ec04c…2071
0xaa3145…feec
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: 0xf96746c0…3bf1db
36 conflicts on slot 0x0000000000…000003
Audit this contract →
← previous block·next block →recent activity