pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#102,683,274
← previous block
next block →
recent activity
Analyzing
Block #102,683,274
10 transactions · 10 stateful · 2026-09-07 06:32:39 UTC
Parallelism
80
/100
Blocked
10
%
Avg conflicts / tx
0.1
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#102,683,274
· 10 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
execOrders
#2
0x3e2e8792
· blocks 1
#3
0x5acec890
#4
0x59558d29
#5
setData
#7
0x6a9e5a8b
#8
0xc7068c7b
#9
execOrders
#6
execFwdPositionOpsV2
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
2
w0
6
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x20b94f7c…2a9b
0x34b655…2a6f
4 touches
1 conflict
0x6c6b3616…04cd
0x34b655…2a6f
4 touches
1 conflict
0xc824469a…6425
0x34b655…2a6f
4 touches
1 conflict
0x14c2d2bc…fc16
0x34b655…2a6f
2 touches
0 conflicts
0x18d8337b…6f07
0x34b655…2a6f
2 touches
0 conflicts
0x26c599c1…706c
0x34b655…2a6f
2 touches
0 conflicts
0x3b4386ab…d3a6
0x34b655…2a6f
2 touches
0 conflicts
0x3fb3f2e2…fef3
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
0x20b94f7c91…602a9b
Audit this contract →
← previous block
·
next block →
recent activity