← previous blocknext block →recent activity
Analyzing
Block #82,728,888
21 transactions · 18 stateful · 2026-06-21 11:25:51 UTC
Parallelism
81/100
Blocked
56%
Avg conflicts / tx
0.9
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #82,728,888 · 21 txs across 4 waves · depth 4
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w24w38w09w110w211w314w016w117w018w119w220w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x22e0cc1d…ad0d
0x34b655…2a6f
8 touches
6 conflicts
0x08913286…f0df
0x34b655…2a6f
8 touches
6 conflicts
0xd98b3c10…67b8
0x34b655…2a6f
8 touches
6 conflicts
0x9d6d6f9f…104f
0xd32edf…ff58
7 touches
6 conflicts
0x4f4bdabd…ffba
0x34b655…2a6f
6 touches
3 conflicts
0x21e43e72…d2f6
0x34b655…2a6f
6 touches
3 conflicts
0x2c75ca93…a569
0x34b655…2a6f
6 touches
3 conflicts
0x326a02b5…8dad
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
6 conflicts on slot 0x22e0cc1d4a…90ad0d
Audit this contract →
← previous block·next block →recent activity