pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#101,975,187
← previous block
next block →
recent activity
Analyzing
Block #101,975,187
13 transactions · 13 stateful · 2026-09-04 18:46:02 UTC
Parallelism
85
/100
Blocked
8
%
Avg conflicts / tx
0.08
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#101,975,187
· 13 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
execOrders
· blocks 1
#2
updatePrices
#3
0x5acec890
#4
0x5acec890
#5
updateDataFeedsValuesPartial
#6
0x59558d29
#7
withdraw
#8
setData
#9
execFwdPositionOpsV2
#10
relay
#12
execOrders
#11
execFwdPositionOpsV2
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
1
w0
11
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x51fc8795…126f
0x34b655…2a6f
4 touches
1 conflict
0x09000000…0007
0x000000…1000
2 touches
0 conflicts
0x0b000000…0002
0x000000…1000
2 touches
0 conflicts
0x04d962b7…1cc0
0x34b655…2a6f
2 touches
0 conflicts
0x0a7b0f17…fb88
0x34b655…2a6f
2 touches
0 conflicts
0x165b15fd…15cb
0x34b655…2a6f
2 touches
0 conflicts
0x266f9b72…25a4
0x34b655…2a6f
2 touches
0 conflicts
0x28468994…9320
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
0x51fc8795c8…57126f
Audit this contract →
← previous block
·
next block →
recent activity