← previous blocknext block →recent activity
Analyzing
Block #82,696,924
27 transactions · 22 stateful · 2026-06-21 07:52:30 UTC
Parallelism
85/100
Blocked
41%
Avg conflicts / tx
0.67
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #82,696,924 · 27 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
1w04w05w06w17w18w29w010w112w014w015w116w218w319w325w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x08913286…f0df
0x34b655…2a6f
8 touches
6 conflicts
0x7cb2f3fa…4836
0x34b655…2a6f
6 touches
3 conflicts
0xfcb9138a…3830
0xc8689a…ee79
6 touches
3 conflicts
0x9fb55ee7…8ecc
0xa6afd3…d132
6 touches
3 conflicts
0xac808a27…82db
0x34b655…2a6f
6 touches
3 conflicts
0xac2a0273…721b
0x34b655…2a6f
6 touches
3 conflicts
0xb1089542…3068
0xd32edf…ff58
5 touches
3 conflicts
0x71e4ffd1…9beb
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 0x08913286f9…0ff0df
Audit this contract →
← previous block·next block →recent activity