pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#102,017,094
← previous block
next block →
recent activity
Analyzing
Block #102,017,094
11 transactions · 11 stateful · 2026-09-04 22:18:34 UTC
Parallelism
82
/100
Blocked
9
%
Avg conflicts / tx
0.09
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#102,017,094
· 11 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
matchOrders
#2
execOrders
#3
0x5acec890
#4
0x5acec890
· blocks 1
#5
0x5acec890
#6
0x59558d29
#7
setData
#9
execFwdPositionOpsV2
#10
0xc7068c7b
#8
execFwdPositionOpsV2
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
4
w0
8
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xfe3d37ee…6e67
0x34b655…2a6f
4 touches
1 conflict
0x65903ef9…2567
0x34b655…2a6f
4 touches
1 conflict
0x766c0128…5cb9
0x34b655…2a6f
4 touches
1 conflict
0x1d9867ad…6d9a
0x34b655…2a6f
2 touches
0 conflicts
0x2c401f11…4904
0x34b655…2a6f
2 touches
0 conflicts
0x31ef4e0d…2944
0x34b655…2a6f
2 touches
0 conflicts
0x36efe59d…0cf4
0x34b655…2a6f
2 touches
0 conflicts
0x3ffa5c6c…f075
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
0xfe3d37ee7e…836e67
Audit this contract →
← previous block
·
next block →
recent activity