pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#102,276,434
← previous block
next block →
recent activity
Analyzing
Block #102,276,434
8 transactions · 8 stateful · 2026-09-05 20:12:59 UTC
Parallelism
75
/100
Blocked
13
%
Avg conflicts / tx
0.13
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#102,276,434
· 8 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
execOrders
#2
0xab083028
#3
0xab083028
#4
0x59558d29
#5
execFwdPositionOpsV2
· blocks 1
#7
execOrders
#6
execFwdPositionOpsV2
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
5
w0
6
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x731d7308…fd26
0x34b655…2a6f
4 touches
1 conflict
0x96259adc…7fed
0x34b655…2a6f
4 touches
1 conflict
0xc824469a…6425
0x34b655…2a6f
4 touches
1 conflict
0x01315072…0e2d
0x34b655…2a6f
2 touches
0 conflicts
0x045532dd…4b7d
0x34b655…2a6f
2 touches
0 conflicts
0x0762cfdd…72fc
0x34b655…2a6f
2 touches
0 conflicts
0x14bfb388…e757
0x34b655…2a6f
2 touches
0 conflicts
0x14c32f7b…724c
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
0x731d73081c…7dfd26
Audit this contract →
← previous block
·
next block →
recent activity