pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#103,223,511
← previous block
next block →
recent activity
Analyzing
Block #103,223,511
11 transactions · 10 stateful · 2026-09-09 03:56:33 UTC
Parallelism
82
/100
Blocked
10
%
Avg conflicts / tx
0.09
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#103,223,511
· 11 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
execOrders
#2
0xab083028
#3
0x0c7abd22
· blocks 1
#4
0x59558d29
#5
0x59558d29
#7
0x3f5c179b
#8
execOrders
#9
0x6aa0d8f5
#10
setData
#6
execFwdPositionOpsV2
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
3
w0
6
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x0044b90d…650b
0x34b655…2a6f
4 touches
1 conflict
0xbcbf5d09…8bac
0x34b655…2a6f
4 touches
1 conflict
0xc824469a…6425
0x34b655…2a6f
4 touches
1 conflict
0x1513b999…b52e
0x34b655…2a6f
2 touches
0 conflicts
0x3a02129f…9eaf
0x34b655…2a6f
2 touches
0 conflicts
0x448fdf2a…fab4
0x34b655…2a6f
2 touches
0 conflicts
0x4b84a880…6abb
0x34b655…2a6f
2 touches
0 conflicts
0x4c2b9b6e…4196
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
0x0044b90d0c…97650b
Audit this contract →
← previous block
·
next block →
recent activity