pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#104,810,841
← previous block
next block →
recent activity
Analyzing
Block #104,810,841
14 transactions · 13 stateful · 2026-09-14 17:48:37 UTC
Parallelism
79
/100
Blocked
15
%
Avg conflicts / tx
0.14
Longest chain
3
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#104,810,841
· 14 txs across 3 waves · depth 3
parallel ↔ serial
wave
w0
wave
w1
wave
w2
#0
syscallReward
#1
0x0c7abd22
#2
execOrders
#3
updateDataFeedsValuesPartial
#4
0x59558d29
#5
0x59558d29
#6
execOrders
· blocks 1
#8
setData
#9
execFwdPositionOpsV2
#11
mintTo
#12
0x6aa83378
#13
execOrders
#7
execOrders
· blocks 1
#10
execFwdPositionOpsV2
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
6
w0
7
w1
10
w2
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x2095236c…26d6
0x34b655…2a6f
4 touches
1 conflict
0x49890ced…6f23
0x34b655…2a6f
4 touches
1 conflict
0x5c455afd…ce06
0x34b655…2a6f
4 touches
1 conflict
0xb550abea…2729
0x34b655…2a6f
4 touches
1 conflict
0x482471ad…122f
0x34b655…2a6f
4 touches
1 conflict
0xc824469a…6425
0x34b655…2a6f
4 touches
1 conflict
0x85fd6655…5013
0x34b655…2a6f
3 touches
1 conflict
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
0x2095236cc9…b126d6
Audit this contract →
← previous block
·
next block →
recent activity