← previous blocknext block →recent activity
Analyzing
Block #82,100,815
38 transactions · 35 stateful · 2026-06-18 13:32:15 UTC
Parallelism
63/100
Blocked
49%
Avg conflicts / tx
2.11
Longest chain
14 deep
Execution timeline
did this block parallelize well?
view
block #82,100,815 · 38 txs across 14 waves · depth 14
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
wave w13
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w011w113w216w017w121w022w123w224w325w426w329w531w732w833w934w1035w1136w1237w13
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xd98b3c10…67b8
0x34b655…2a6f
20 touches
45 conflicts
0xc824469a…6425
0x34b655…2a6f
12 touches
15 conflicts
0xe6e6f436…ddc0
0x34b655…2a6f
12 touches
15 conflicts
0x08913286…f0df
0x34b655…2a6f
10 touches
10 conflicts
0xac2a0273…721b
0x34b655…2a6f
8 touches
6 conflicts
0x22e0cc1d…ad0d
0x34b655…2a6f
8 touches
6 conflicts
0x6fbc2e5a…e69c
0x34b655…2a6f
6 touches
3 conflicts
0x7ce93f3d…b70e
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
45 conflicts on slot 0xd98b3c102b…ca67b8
Audit this contract →
← previous block·next block →recent activity