← previous blocknext block →recent activity
Analyzing
Block #81,479,563
39 transactions · 34 stateful · 2026-06-15 16:30:19 UTC
Parallelism
80/100
Blocked
59%
Avg conflicts / tx
1.44
Longest chain
8 deep
Execution timeline
did this block parallelize well?
view
block #81,479,563 · 39 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
1w02w13w24w15w26w37w08w19w210w311w412w519w5
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xd98b3c10…67b8
0x34b655…2a6f
14 touches
21 conflicts
0x00000000…003d
0xa6afd3…d132
10 touches
10 conflicts
0xacdf56b3…e33c
0xa6afd3…d132
10 touches
10 conflicts
0xf2f76ab3…623e
0x2a68ba…90c5
8 touches
6 conflicts
0x00000000…0018
0x1b6862…e19c
6 touches
3 conflicts
0x00000000…0028
0x1b6862…e19c
6 touches
3 conflicts
0xba5743c7…21bf
0x1b6862…e19c
6 touches
3 conflicts
0xd9f18d9a…141d
0x1b6862…e19c
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
21 conflicts on slot 0xd98b3c102b…ca67b8
Audit this contract →
← previous block·next block →recent activity