pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#101,663,423
← previous block
next block →
recent activity
Analyzing
Block #101,663,423
13 transactions · 12 stateful · 2026-09-03 16:34:22 UTC
Parallelism
85
/100
Blocked
17
%
Avg conflicts / tx
0.15
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#101,663,423
· 13 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
0x6a99a206
#2
execOrder
· blocks 1
#3
updatePrices
· blocks 1
#5
execOrders
#6
0x59558d29
#7
executeBatch
#8
setData
#10
0x57368ddf
#11
execFwdPositionOpsV2
#12
execOrders
#4
updatePrices
#9
execFwdPositionOpsV2
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
2
w0
3
w0
4
w1
9
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x20b1228b…2487
0x34b655…2a6f
4 touches
1 conflict
0xc824469a…6425
0x34b655…2a6f
4 touches
1 conflict
0x00000000…0002
0xf5b5f7…6d70
4 touches
1 conflict
0x17bb579f…938c
0x34b655…2a6f
2 touches
0 conflicts
0x19f59494…c7f1
0x34b655…2a6f
2 touches
0 conflicts
0x24ed74ea…a3ff
0x34b655…2a6f
2 touches
0 conflicts
0x28cf9680…8550
0x34b655…2a6f
2 touches
0 conflicts
0x375b6201…9c1e
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
0x20b1228bdf…a72487
Audit this contract →
← previous block
·
next block →
recent activity