← previous blocknext block →recent activity
Analyzing
Block #80,822,841
47 transactions · 37 stateful · 2026-06-12 15:35:15 UTC
Parallelism
79/100
Blocked
57%
Avg conflicts / tx
1.51
Longest chain
10 deep
Execution timeline
did this block parallelize well?
view
block #80,822,841 · 47 txs across 10 waves · depth 10
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
wave w7
wave w8
wave w9
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w24w35w46w511w114w416w422w423w528w6
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xd98b3c10…67b8
0x34b655…2a6f
18 touches
36 conflicts
0xa7340bc7…f2e5
0xd32edf…ff58
13 touches
21 conflicts
0x00ddbbf2…4588
0x34b655…2a6f
10 touches
10 conflicts
0x22e0cc1d…ad0d
0x34b655…2a6f
10 touches
10 conflicts
0x7ee6007b…fd68
0x34b655…2a6f
8 touches
6 conflicts
0x3a3097d7…2ab5
0x1b6862…e19c
6 touches
3 conflicts
0xd9f18d9a…141d
0x1b6862…e19c
6 touches
3 conflicts
0x170e4e4c…2b90
0x34b655…2a6f
6 touches
3 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: Perpl
36 conflicts on slot 0xd98b3c102b…ca67b8
Audit this contract →
← previous block·next block →recent activity