← previous blocknext block →recent activity
Analyzing
Block #82,520,269
42 transactions · 29 stateful · 2026-06-20 12:10:10 UTC
Parallelism
90/100
Blocked
48%
Avg conflicts / tx
0.6
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #82,520,269 · 42 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
4w06w07w08w19w110w113w216w317w218w319w022w126w027w128w229w334w337w140w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x08913286…f0df
0x34b655…2a6f
8 touches
6 conflicts
0xf9f48af5…4205
0xa6afd3…d132
8 touches
6 conflicts
0x26470289…bb21
0xa6afd3…d132
6 touches
3 conflicts
0x664bf99e…0a8c
0x34b655…2a6f
6 touches
3 conflicts
0xfcb9138a…3830
0xc8689a…ee79
6 touches
3 conflicts
0x6f6fc26c…3e34
0x34b655…2a6f
6 touches
3 conflicts
0xab83f300…f8c8
0x34b655…2a6f
6 touches
3 conflicts
0xac2a0273…721b
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 0x08913286f9…0ff0df
Audit this contract →
← previous block·next block →recent activity