pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#102,009,414
← previous block
next block →
recent activity
Analyzing
Block #102,009,414
12 transactions · 12 stateful · 2026-09-04 21:39:42 UTC
Parallelism
83
/100
Blocked
8
%
Avg conflicts / tx
0.08
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#102,009,414
· 12 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
matchOrders
· blocks 1
#3
updatePrices
#4
0xab083028
#5
0xab083028
#6
setData
#7
0x59558d29
#8
execFwdPositionOpsV2
#9
execFwdPositionOpsV2
#10
updateTemporalNumericValuesV1
#11
execOrders
#2
matchOrders
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
1
w0
2
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x8881a9a9…b1ac
0x99c7a7…8bf0
4 touches
1 conflict
0xde93ff88…37ec
0x754704…b603
4 touches
1 conflict
0x32070dd0…692b
0x754704…b603
4 touches
1 conflict
0x5cb99fee…00cf
0x754704…b603
4 touches
1 conflict
0x3dbaed38…1c8a
0x99c7a7…8bf0
4 touches
1 conflict
0x09106a95…1467
0x33176b…e078
2 touches
0 conflicts
0x198ff0c2…43dc
0x34b655…2a6f
2 touches
0 conflicts
0x22e0cc1d…ad0d
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:
0x99c7a72e…c78bf0
1 conflict on slot
0x8881a9a9d2…f4b1ac
Audit this contract →
← previous block
·
next block →
recent activity