← previous blocknext block →recent activity
Analyzing
Block #82,966,015
21 transactions · 16 stateful · 2026-06-22 13:50:02 UTC
Parallelism
76/100
Blocked
56%
Avg conflicts / tx
0.86
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #82,966,015 · 21 txs across 5 waves · depth 5
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w04w05w18w09w110w211w312w114w216w319w320w4
- 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
0xff98d0f5…46f6
0x34b655…2a6f
6 touches
3 conflicts
0x6779811e…481e
0x34b655…2a6f
6 touches
3 conflicts
0x61684cf2…e923
0x34b655…2a6f
6 touches
3 conflicts
0x90d81b88…3a34
0x34b655…2a6f
5 touches
3 conflicts
0xc3688185…9b36
0x34b655…2a6f
4 touches
1 conflict
0xc5e7a2e8…516a
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 0x22e0cc1d4a…90ad0d
Audit this contract →
← previous block·next block →recent activity