pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#102,043,308
← previous block
next block →
recent activity
Analyzing
Block #102,043,308
12 transactions · 12 stateful · 2026-09-05 00:31:17 UTC
Parallelism
83
/100
Blocked
17
%
Avg conflicts / tx
0.17
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#102,043,308
· 12 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
0xb5ce855a
#2
0x5acec890
#3
execOrder
· blocks 1
#4
0x59558d29
#5
setData
#6
execFwdPositionOpsV2
#8
forward
#9
transfer
· blocks 1
#11
execOrders
#7
execFwdPositionOpsV2
#10
transfer
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
3
w0
7
w1
9
w0
10
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xc852b267…9d14
0x34b655…2a6f
4 touches
1 conflict
0x42041fec…bd86
0x754704…b603
4 touches
1 conflict
0x0b000000…0002
0x000000…1000
2 touches
0 conflicts
0xa4d64f50…4f7c
0x0e60e4…36ef
2 touches
0 conflicts
0x09106a95…1467
0x33176b…e078
2 touches
0 conflicts
0x00000000…00c9
0x34b655…2a6f
2 touches
0 conflicts
0x0db691ab…3ee3
0x34b655…2a6f
2 touches
0 conflicts
0x1f396cee…862f
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
0xc852b26715…339d14
Audit this contract →
← previous block
·
next block →
recent activity