pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#102,435,656
← previous block
next block →
recent activity
Analyzing
Block #102,435,656
12 transactions · 12 stateful · 2026-09-06 09:39:40 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,435,656
· 12 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
matchOrders
· blocks 1
#3
0xab083028
#4
0xab083028
#5
0x5acec890
#6
0x59558d29
#7
execFwdPositionOpsV2
#8
setData
#9
execFwdPositionOpsV2
#10
0x6a9d34df
#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
0xcf570cc1…b19c
0x99c7a7…8bf0
4 touches
1 conflict
0xd52cdd17…928b
0x99c7a7…8bf0
4 touches
1 conflict
0x5f0647bd…59b9
0x754704…b603
4 touches
1 conflict
0xa165a1e5…67be
0x754704…b603
4 touches
1 conflict
0xce62e150…1e09
0x754704…b603
4 touches
1 conflict
0xca841faa…486a
0x34b655…2a6f
2 touches
0 conflicts
0xd2ce3347…ae39
0x34b655…2a6f
2 touches
0 conflicts
0x792d0a3d…960e
0x37db7f…ec7b
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
0xcf570cc1e6…31b19c
Audit this contract →
← previous block
·
next block →
recent activity