pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#101,266,020
← previous block
next block →
recent activity
Analyzing
Block #101,266,020
13 transactions · 11 stateful · 2026-09-02 07:14:54 UTC
Parallelism
85
/100
Blocked
18
%
Avg conflicts / tx
0.15
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#101,266,020
· 13 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
0x5acec890
· blocks 2
#2
0x5acec890
#4
0x59558d29
#5
0x59558d29
#6
setData
#7
execFwdPositionOpsV2
#8
forward
#9
transfer
#10
0x6a97cd66
#11
0x142d7d…e46c
#3
0x3e2e8792
#12
execOrders
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
1
w0
3
w1
12
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xca841faa…486a
0x34b655…2a6f
4 touches
1 conflict
0x51fc8795…126f
0x34b655…2a6f
4 touches
1 conflict
0xc09b0a80…0258
0x34b655…2a6f
4 touches
1 conflict
0x0d974869…426f
0x34b655…2a6f
2 touches
0 conflicts
0x1b723e2a…24bb
0x34b655…2a6f
2 touches
0 conflicts
0x268b8107…1a71
0x34b655…2a6f
2 touches
0 conflicts
0x2fe8ffbf…b6e8
0x34b655…2a6f
2 touches
0 conflicts
0x3d13406e…eff1
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
0xca841faae5…71486a
Audit this contract →
← previous block
·
next block →
recent activity