← previous blocknext block →recent activity
Analyzing
Block #80,833,414
39 transactions · 34 stateful · 2026-06-12 16:45:50 UTC
Parallelism
82/100
Blocked
38%
Avg conflicts / tx
1.03
Longest chain
7 deep
Execution timeline
did this block parallelize well?
view
block #80,833,414 · 39 txs across 7 waves · depth 7
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w03w05w17w210w012w113w314w417w021w524w129w030w131w232w333w434w536w6
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xd98b3c10…67b8
0x34b655…2a6f
14 touches
21 conflicts
0xbd5ba724…3a7c
0xd32edf…ff58
9 touches
10 conflicts
0x00ddbbf2…4588
0x34b655…2a6f
8 touches
6 conflicts
0x00000000…003d
0x065c9d…c394
6 touches
3 conflicts
0x80afd9d9…57cf
0x065c9d…c394
6 touches
3 conflicts
0x00000000…001b
0x1b6862…e19c
4 touches
1 conflict
0xcb45d9d6…cb83
0x1b6862…e19c
4 touches
1 conflict
0xd9f18d9a…141d
0x1b6862…e19c
4 touches
1 conflict
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: Perpl
21 conflicts on slot 0xd98b3c102b…ca67b8
Audit this contract →
← previous block·next block →recent activity