pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#105,617,580
← previous block
next block →
recent activity
Analyzing
Block #105,617,580
14 transactions · 14 stateful · 2026-09-17 13:29:49 UTC
Parallelism
86
/100
Blocked
14
%
Avg conflicts / tx
0.14
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#105,617,580
· 14 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
0x0c7abd22
· blocks 1
#3
handleOp
#4
execOrders
#5
0x59558d29
#6
setData
#7
execOrders
· blocks 1
#9
execFwdPositionOpsV2
#10
forward
#11
0x57368ddf
#12
0x61d59c2d
#13
execOrders
#2
0x0c7abd22
#8
execOrders
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
1
w0
2
w1
7
w0
8
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x713d4d00…b7be
0x34b655…2a6f
4 touches
1 conflict
0xf346808d…6ad4
0x34b655…2a6f
4 touches
1 conflict
0xb719fe58…8381
0x34b655…2a6f
4 touches
1 conflict
0x90a021f0…f922
0x34b655…2a6f
4 touches
1 conflict
0x00000000…0012
0x1b6862…e19c
4 touches
1 conflict
0x00000000…0013
0x1b6862…e19c
4 touches
1 conflict
0x00000000…0015
0x1b6862…e19c
4 touches
1 conflict
0x00000000…001b
0x1b6862…e19c
4 touches
1 conflict
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
0x713d4d0013…1ab7be
Audit this contract →
← previous block
·
next block →
recent activity