← previous blocknext block →recent activity
Analyzing
Block #83,668,628
22 transactions · 14 stateful · 2026-06-25 20:04:08 UTC
Parallelism
82/100
Blocked
36%
Avg conflicts / tx
0.41
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #83,668,628 · 22 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
7w08w111w215w016w117w221w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xde696e46…6446
0x34b655…2a6f
6 touches
3 conflicts
0xb670a63e…ead8
0x34b655…2a6f
5 touches
3 conflicts
0x482471ad…122f
0x34b655…2a6f
4 touches
1 conflict
0x4e1ce17e…98a7
0x34b655…2a6f
4 touches
1 conflict
0x5065feee…34f7
0x34b655…2a6f
4 touches
1 conflict
0x55fa231d…755a
0x34b655…2a6f
4 touches
1 conflict
0x5f96e827…8ed2
0x34b655…2a6f
4 touches
1 conflict
0x737acb78…fce8
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
3 conflicts on slot 0xde696e4658…1e6446
Audit this contract →
← previous block·next block →recent activity