← previous blocknext block →recent activity
Analyzing
Block #82,974,930
25 transactions · 22 stateful · 2026-06-22 14:49:40 UTC
Parallelism
68/100
Blocked
68%
Avg conflicts / tx
1.48
Longest chain
8 deep
Execution timeline
did this block parallelize well?
view
block #82,974,930 · 25 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
1w02w13w24w35w06w28w09w110w211w312w313w414w515w318w422w623w7
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x49d02518…ca01
0x34b655…2a6f
10 touches
10 conflicts
0xf324b405…ca30
0x34b655…2a6f
8 touches
6 conflicts
0x08913286…f0df
0x34b655…2a6f
8 touches
6 conflicts
0x22e0cc1d…ad0d
0x34b655…2a6f
8 touches
6 conflicts
0xd98b3c10…67b8
0x34b655…2a6f
8 touches
6 conflicts
0x00000000…002e
0x1b6862…e19c
6 touches
3 conflicts
0x5a3732cb…edb2
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
10 conflicts on slot 0x49d02518bb…c7ca01
Audit this contract →
← previous block·next block →recent activity