pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#101,500,666
← previous block
next block →
recent activity
Analyzing
Block #101,500,666
15 transactions · 10 stateful · 2026-09-03 02:55:36 UTC
Parallelism
87
/100
Blocked
10
%
Avg conflicts / tx
0.07
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#101,500,666
· 15 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
0x6a98e220
#2
0xa96df62f
#3
updatePrices
· blocks 1
#4
updatePrices
#6
execOrders
#7
0x41a8f47c
#8
approve
#9
execFwdPositionOpsV2
#10
execFwdPositionOpsV2
#11
0x6a98e220
#12
setData
#13
setData
#14
setData
#5
updatePrices
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
3
w0
5
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
0x0a809ce1…7894
0x34b655…2a6f
2 touches
0 conflicts
0x24bb46f7…3853
0x34b655…2a6f
2 touches
0 conflicts
0x2d071de0…c86e
0x34b655…2a6f
2 touches
0 conflicts
0x38357a83…33d2
0x34b655…2a6f
2 touches
0 conflicts
0x3c0e1ae4…59f1
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