pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#85,344,106
← previous block
next block →
recent activity
Analyzing
Block #85,344,106
11 transactions · 11 stateful · 2026-07-03 14:14:21 UTC
Parallelism
73
/100
Blocked
27
%
Avg conflicts / tx
0.27
Longest chain
3
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#85,344,106
· 11 txs across 3 waves · depth 3
parallel ↔ serial
wave
w0
wave
w1
wave
w2
#0
syscallReward
#1
0x938bf18e
#2
updateDataFeedsValuesPartial
#3
execFwdPositionOps
· blocks 1
#4
0xd10227eb
· blocks 1
#6
forward
#7
0x6df9e92b
#8
setData
#5
0x366fe5db
#9
execOrders
· blocks 1
#10
execOrders
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
3
w0
4
w0
5
w1
9
w1
10
w2
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x9916a36a…514d
0x34b655…2a6f
4 touches
1 conflict
0xa20a130c…5d59
0x34b655…2a6f
4 touches
1 conflict
0xd98b3c10…67b8
0x34b655…2a6f
4 touches
1 conflict
0x00bac013…a28c
0xfd44b3…00d1
4 touches
1 conflict
0x00000000…0000
0x354d92…66fb
2 touches
0 conflicts
0x00000000…0001
0x354d92…66fb
2 touches
0 conflicts
0x00000000…0005
0x354d92…66fb
2 touches
0 conflicts
0x09000000…0001
0x000000…1000
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
0x9916a36a8e…99514d
Audit this contract →
← previous block
·
next block →
recent activity