pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#101,854,652
← previous block
next block →
recent activity
Analyzing
Block #101,854,652
10 transactions · 8 stateful · 2026-09-04 08:36:14 UTC
Parallelism
70
/100
Blocked
50
%
Avg conflicts / tx
0.5
Longest chain
3
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#101,854,652
· 10 txs across 3 waves · depth 3
parallel ↔ serial
wave
w0
wave
w1
wave
w2
#0
syscallReward
#1
0x0c7abd22
#2
0x0c7abd22
· blocks 2
#4
execOrder
· blocks 2
#6
execOrders
#7
setData
#3
0x0c7abd22
#5
execOrders
· blocks 1
#8
0xf99cae99
#9
execFwdPositionOpsV2
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
2
w0
3
w1
4
w0
5
w1
8
w1
9
w2
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x3836a730…b3a9
0x34b655…2a6f
6 touches
3 conflicts
0xf9da5665…2703
0x754704…b603
4 touches
1 conflict
0x846f2172…fd54
0x0555e3…2b9c
4 touches
1 conflict
0x8e80434a…a96d
0x0555e3…2b9c
4 touches
1 conflict
0x0259425f…039f
0x2d82ac…5fd8
4 touches
1 conflict
0x00000000…0001
0x2d82ac…5fd8
4 touches
1 conflict
0x00000000…0012
0x1b6862…e19c
4 touches
1 conflict
0x00000000…0013
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
3 conflicts on slot
0x3836a73066…21b3a9
Audit this contract →
← previous block
·
next block →
recent activity