pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#102,053,287
← previous block
next block →
recent activity
Analyzing
Block #102,053,287
12 transactions · 10 stateful · 2026-09-05 01:21:50 UTC
Parallelism
83
/100
Blocked
10
%
Avg conflicts / tx
0.08
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#102,053,287
· 12 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
0x5acec890
#2
0xab083028
#3
0xab083028
#4
0x5acec890
#5
execOrder
· blocks 1
#6
0x59558d29
#7
execPerpOps
#8
execPerpOps
#9
setData
#10
execFwdPositionOpsV2
#11
execFwdPositionOpsV2
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
5
w0
11
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xd29e547b…a1dd
0x34b655…2a6f
4 touches
1 conflict
0xd66696e0…0842
0x34b655…2a6f
4 touches
1 conflict
0x4402c2ee…a884
0x34b655…2a6f
3 touches
1 conflict
0x045532dd…4b7d
0x34b655…2a6f
2 touches
0 conflicts
0x0763c790…8288
0x34b655…2a6f
2 touches
0 conflicts
0x19f8e68c…4f86
0x34b655…2a6f
2 touches
0 conflicts
0x29a58269…011a
0x34b655…2a6f
2 touches
0 conflicts
0x3204793c…e4f7
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
0xd29e547b5d…35a1dd
Audit this contract →
← previous block
·
next block →
recent activity