pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#106,190,420
← previous block
next block →
recent activity
Analyzing
Block #106,190,420
12 transactions · 11 stateful · 2026-09-19 13:35:22 UTC
Parallelism
83
/100
Blocked
9
%
Avg conflicts / tx
0.08
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#106,190,420
· 12 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
matchOrders
#2
execOrder
· blocks 1
#4
execOrders
#5
updatePrices
#6
0x3e2e8792
#7
updateDataFeedsValuesPartial
#8
transferWithAuthorization
#9
setData
#10
execFwdPositionOpsV2
#11
execOrders
#3
execOrder
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
2
w0
3
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x708d7a74…09e3
0x34b655…2a6f
4 touches
1 conflict
0x09000000…0007
0x000000…1000
2 touches
0 conflicts
0x0b000000…0002
0x000000…1000
2 touches
0 conflicts
0x1321736a…43e3
0x34b655…2a6f
2 touches
0 conflicts
0x1c5aed73…e93c
0x34b655…2a6f
2 touches
0 conflicts
0x62ecdc97…63eb
0x34b655…2a6f
2 touches
0 conflicts
0x64a785e4…0110
0x34b655…2a6f
2 touches
0 conflicts
0x90fa3fa2…3879
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
0x708d7a74a7…5d09e3
Audit this contract →
← previous block
·
next block →
recent activity