← previous blocknext block →recent activity
Analyzing
Block #82,975,253
18 transactions · 16 stateful · 2026-06-22 14:51:50 UTC
Parallelism
72/100
Blocked
38%
Avg conflicts / tx
0.72
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #82,975,253 · 18 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
2w03w14w25w06w07w08w19w113w316w017w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xb4bc16a4…4825
0x34b655…2a6f
7 touches
6 conflicts
0x8e507257…71c1
0x34b655…2a6f
6 touches
3 conflicts
0x9a3068dd…18f0
0x34b655…2a6f
6 touches
3 conflicts
0x2eb3373a…8aff
0x34b655…2a6f
6 touches
3 conflicts
0x08913286…f0df
0x34b655…2a6f
6 touches
3 conflicts
0x22e0cc1d…ad0d
0x34b655…2a6f
6 touches
3 conflicts
0x36a49c16…89b9
0xc8689a…ee79
6 touches
3 conflicts
0x82dd2252…e1ce
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 0xb4bc16a4d9…154825
Audit this contract →
← previous block·next block →recent activity