pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#106,367,516
← previous block
next block →
recent activity
Analyzing
Block #106,367,516
8 transactions · 8 stateful · 2026-09-20 04:26:42 UTC
Parallelism
63
/100
Blocked
38
%
Avg conflicts / tx
0.5
Longest chain
3
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#106,367,516
· 8 txs across 3 waves · depth 3
parallel ↔ serial
wave
w0
wave
w1
wave
w2
#0
syscallReward
#1
0x0c7abd22
#2
0x4cb2db39
#3
execFwdPositionOpsV2
· blocks 1
#4
0xffb62b9c
· blocks 2
#5
0xffb62b9c
· blocks 1
#7
execOrders
#6
0xffb62b9c
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
3
w0
4
w0
5
w1
6
w2
7
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x9c56643d…ee77
0x5be4ee…673f
6 touches
3 conflicts
0x9c56643d…ee85
0x5be4ee…673f
6 touches
3 conflicts
0xc8f755b6…7b04
0x34b655…2a6f
4 touches
1 conflict
0x00000000…003d
0x065c9d…c394
2 touches
0 conflicts
0x00000000…0012
0x1b6862…e19c
2 touches
0 conflicts
0x00000000…0013
0x1b6862…e19c
2 touches
0 conflicts
0x00000000…0015
0x1b6862…e19c
2 touches
0 conflicts
0x00000000…001a
0x1b6862…e19c
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:
0x5be4ee8b…b7673f
3 conflicts on slot
0x9c56643d01…37ee77
Audit this contract →
← previous block
·
next block →
recent activity