← previous blocknext block →recent activity
Analyzing
Block #80,707,365
36 transactions · 29 stateful · 2026-06-12 02:45:12 UTC
Parallelism
64/100
Blocked
62%
Avg conflicts / tx
2.25
Longest chain
13 deep
Execution timeline
did this block parallelize well?
view
block #80,707,365 · 36 txs across 13 waves · depth 13
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
wave w7
wave w8
wave w9
wave w10
wave w11
wave w12
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w06w07w18w09w110w211w313w014w115w019w120w023w125w226w327w428w529w630w731w832w933w1034w11
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xd98b3c10…67b8
0x34b655…2a6f
24 touches
66 conflicts
0x22e0cc1d…ad0d
0x34b655…2a6f
12 touches
15 conflicts
0xd11dc26e…59ab
0x34b655…2a6f
10 touches
10 conflicts
0xc5a1b2fe…5369
0x34b655…2a6f
10 touches
10 conflicts
0x6fbc2e5a…e69c
0x34b655…2a6f
8 touches
6 conflicts
0x00ddbbf2…4588
0x34b655…2a6f
8 touches
6 conflicts
0x01414ad2…98ec
0x34b655…2a6f
8 touches
6 conflicts
0x326a02b5…8dad
0x34b655…2a6f
8 touches
6 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
66 conflicts on slot 0xd98b3c102b…ca67b8
Audit this contract →
← previous block·next block →recent activity