pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#101,799,459
← previous block
next block →
recent activity
Analyzing
Block #101,799,459
13 transactions · 11 stateful · 2026-09-04 03:58:36 UTC
Parallelism
85
/100
Blocked
9
%
Avg conflicts / tx
0.08
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#101,799,459
· 13 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
0x6a9a4264
#2
updatePrices
· blocks 1
#3
updatePrices
#5
0x5acec890
#6
0x59558d29
#7
setData
#8
execFwdPositionOpsV2
#9
execFwdPositionOpsV2
#10
execFwdPositionOpsV2
#11
0x6a9a4264
#12
execOrders
#4
updatePrices
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
2
w0
4
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…0002
0xf5b5f7…6d70
4 touches
1 conflict
0x09000000…0007
0x000000…1000
2 touches
0 conflicts
0x0b000000…0002
0x000000…1000
2 touches
0 conflicts
0x09106a95…1467
0x33176b…e078
2 touches
0 conflicts
0x05e25943…dd95
0x34b655…2a6f
2 touches
0 conflicts
0x097bb32f…dde8
0x34b655…2a6f
2 touches
0 conflicts
0x20b1228b…2487
0x34b655…2a6f
2 touches
0 conflicts
0x2bb0d58d…9dcf
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:
0xf5b5f7f8…a36d70
1 conflict on slot
0x0000000000…000002
Audit this contract →
← previous block
·
next block →
recent activity