pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#83,868,754
← previous block
next block →
recent activity
Analyzing
Block #83,868,754
11 transactions · 9 stateful · 2026-06-26 18:19:31 UTC
Parallelism
82
/100
Blocked
22
%
Avg conflicts / tx
0.18
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#83,868,754
· 11 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
0x6a3ec32b
#2
exactInputSingle
#3
execFwdPositionOps
· blocks 1
#4
execFwdPositionOps
#5
0xc5a04723
#7
setData
#8
execOrders
· blocks 1
#10
execOrders
#6
execFwdPositionOps
#9
execOrders
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
3
w0
6
w1
8
w0
9
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x286711a5…b3bf
0x34b655…2a6f
4 touches
1 conflict
0x90a9e3f8…17ab
0x34b655…2a6f
4 touches
1 conflict
0xc6356626…bc30
0x34b655…2a6f
4 touches
1 conflict
0xd98b3c10…67b8
0x34b655…2a6f
4 touches
1 conflict
0xfab1627b…b819
0x34b655…2a6f
4 touches
1 conflict
0x307414a5…7214
0x34b655…2a6f
4 touches
1 conflict
0x4cc660ec…6603
0x34b655…2a6f
2 touches
0 conflicts
0x5c0393a4…8b86
0x34b655…2a6f
2 touches
0 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
1 conflict on slot
0x286711a50a…edb3bf
Audit this contract →
← previous block
·
next block →
recent activity