← previous blocknext block →recent activity
Analyzing
Block #82,970,755
24 transactions · 19 stateful · 2026-06-22 14:21:44 UTC
Parallelism
83/100
Blocked
47%
Avg conflicts / tx
0.63
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #82,970,755 · 24 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
2w03w04w19w010w111w212w314w215w017w118w122w123w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x08913286…f0df
0x34b655…2a6f
8 touches
6 conflicts
0x54b193ad…c830
0x34b655…2a6f
6 touches
3 conflicts
0xfc3d5171…8357
0x34b655…2a6f
6 touches
3 conflicts
0x664bf99e…0a8c
0x34b655…2a6f
6 touches
3 conflicts
0xab83f300…f8c8
0x34b655…2a6f
6 touches
3 conflicts
0x518f2037…e422
0xa6afd3…d132
6 touches
3 conflicts
0xc824469a…6425
0x34b655…2a6f
6 touches
3 conflicts
0xfcb9138a…3830
0xc8689a…ee79
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