← previous blocknext block →recent activity
Analyzing
Block #80,683,947
19 transactions · 18 stateful · 2026-06-12 00:09:06 UTC
Parallelism
58/100
Blocked
61%
Avg conflicts / tx
2
Longest chain
8 deep
Execution timeline
did this block parallelize well?
view
block #80,683,947 · 19 txs across 8 waves · depth 8
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
wave w7
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
5w06w17w28w39w411w012w113w214w315w416w517w618w7
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xd98b3c10…67b8
0x34b655…2a6f
16 touches
28 conflicts
0x00000000…0002
0x019883…2a9a
10 touches
10 conflicts
0x00000000…0003
0x019883…2a9a
10 touches
10 conflicts
0x44ad89ba…cf83
0x0cc9b2…7777
10 touches
10 conflicts
0x99a3a7c1…1e2b
0x0cc9b2…7777
10 touches
10 conflicts
0x00000000…0000
0x019883…2a9a
10 touches
10 conflicts
0x22e0cc1d…ad0d
0x34b655…2a6f
10 touches
10 conflicts
0x326a02b5…8dad
0x34b655…2a6f
10 touches
10 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
28 conflicts on slot 0xd98b3c102b…ca67b8
Audit this contract →
← previous block·next block →recent activity