← previous blocknext block →recent activity
Analyzing
Block #82,725,873
20 transactions · 15 stateful · 2026-06-21 11:05:40 UTC
Parallelism
70/100
Blocked
53%
Avg conflicts / tx
0.7
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #82,725,873 · 20 txs across 6 waves · depth 6
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w14w06w210w311w114w215w317w418w5
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xc68d6f14…bdde
0x34b655…2a6f
8 touches
6 conflicts
0xd98b3c10…67b8
0x34b655…2a6f
6 touches
3 conflicts
0x00000000…003d
0xa6afd3…d132
6 touches
3 conflicts
0x26470289…bb21
0xa6afd3…d132
6 touches
3 conflicts
0x3912a14f…3ba1
0x34b655…2a6f
4 touches
1 conflict
0x4ec9ff52…e6f7
0x34b655…2a6f
4 touches
1 conflict
0x6a53b1c0…c3f2
0x34b655…2a6f
4 touches
1 conflict
0x737acb78…fce8
0x34b655…2a6f
4 touches
1 conflict
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
6 conflicts on slot 0xc68d6f1433…40bdde
Audit this contract →
← previous block·next block →recent activity