← previous blocknext block →recent activity
Analyzing
Block #83,026,697
23 transactions · 21 stateful · 2026-06-22 20:35:59 UTC
Parallelism
57/100
Blocked
48%
Avg conflicts / tx
1.35
Longest chain
10 deep
Execution timeline
did this block parallelize well?
view
block #83,026,697 · 23 txs across 10 waves · depth 10
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
wave w7
wave w8
wave w9
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w03w14w25w36w47w58w613w120w721w8
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x926eb04e…d1cd
0x34b655…2a6f
14 touches
21 conflicts
0xffb8950c…23c6
0x34b655…2a6f
14 touches
21 conflicts
0x36a49c16…89b9
0xc8689a…ee79
14 touches
21 conflicts
0x22e0cc1d…ad0d
0x34b655…2a6f
14 touches
21 conflicts
0x08913286…f0df
0x34b655…2a6f
14 touches
21 conflicts
0x8e5cc690…b06b
0x34b655…2a6f
14 touches
21 conflicts
0xf7e84d35…ad5c
0x34b655…2a6f
14 touches
21 conflicts
0x60c7217a…8c94
0x34b655…2a6f
10 touches
14 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
21 conflicts on slot 0x926eb04ec2…f6d1cd
Audit this contract →
← previous block·next block →recent activity