pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#101,937,357
← previous block
next block →
recent activity
Analyzing
Block #101,937,357
10 transactions · 9 stateful · 2026-09-04 15:34:13 UTC
Parallelism
80
/100
Blocked
11
%
Avg conflicts / tx
0.1
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#101,937,357
· 10 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
0x5acec890
#2
0x59558d29
#3
execFwdPositionOpsV2
· blocks 1
#4
execFwdPositionOpsV2
#5
transfer
#6
0x6a9ae56c
#7
setData
#8
0x61633731
#9
execOrders
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
3
w0
9
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xbd590df7…9891
0x34b655…2a6f
4 touches
1 conflict
0xbc8fb280…76a3
0x34b655…2a6f
4 touches
1 conflict
0xcdcaadcf…1c9f
0x34b655…2a6f
4 touches
1 conflict
0xe1c4e5ce…0dec
0x34b655…2a6f
4 touches
1 conflict
0x11db128b…1153
0x34b655…2a6f
2 touches
0 conflicts
0x2bcdd6f4…5253
0x34b655…2a6f
2 touches
0 conflicts
0x3ffc6612…852a
0x34b655…2a6f
2 touches
0 conflicts
0x4a5956ef…e226
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
0xbd590df7f7…cf9891
Audit this contract →
← previous block
·
next block →
recent activity