pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#84,576,175
← previous block
next block →
recent activity
Analyzing
Block #84,576,175
12 transactions · 9 stateful · 2026-06-30 00:54:09 UTC
Parallelism
75
/100
Blocked
22
%
Avg conflicts / tx
0.25
Longest chain
3
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#84,576,175
· 12 txs across 3 waves · depth 3
parallel ↔ serial
wave
w0
wave
w1
wave
w2
#0
syscallReward
#1
execFwdPositionOps
#2
0x9e76c652
#3
updateDataFeedsValuesPartial
#4
updateDataFeedsValuesPartial
#5
0x6a431429
#6
setData
#7
exactInputSingle
#8
execOrders
· blocks 2
#10
execOrders
#9
execOrders
· blocks 1
#11
execOrders
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
8
w0
9
w1
11
w2
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xd98b3c10…67b8
0x34b655…2a6f
6 touches
3 conflicts
0x7b7a78ce…a432
0x34b655…2a6f
4 touches
1 conflict
0x429718a4…f345
0x34b655…2a6f
4 touches
1 conflict
0xa9ad4c70…1120
0x34b655…2a6f
4 touches
1 conflict
0xe4df7573…6ac5
0x34b655…2a6f
4 touches
1 conflict
0xe59df86b…a00c
0x34b655…2a6f
4 touches
1 conflict
0x9966da31…0d0f
0x34b655…2a6f
4 touches
1 conflict
0x9a3068dd…18f0
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
3 conflicts on slot
0xd98b3c102b…ca67b8
Audit this contract →
← previous block
·
next block →
recent activity