pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#101,815,815
← previous block
next block →
recent activity
Analyzing
Block #101,815,815
12 transactions · 12 stateful · 2026-09-04 05:20:52 UTC
Parallelism
83
/100
Blocked
17
%
Avg conflicts / tx
0.17
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#101,815,815
· 12 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
updatePrices
#2
0x5acec890
#3
0x5acec890
· blocks 1
#5
0x5acec890
#6
0x59558d29
#7
execFwdPositionOpsV2
#8
0x6a9a55ac
#9
setData
#10
execOrders
· blocks 1
#4
0x5acec890
#11
execOrders
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
3
w0
4
w1
10
w0
11
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xca841faa…486a
0x34b655…2a6f
4 touches
1 conflict
0xd98b3c10…67b8
0x34b655…2a6f
4 touches
1 conflict
0x0b000000…0002
0x000000…1000
2 touches
0 conflicts
0x03da5c00…b353
0x34b655…2a6f
2 touches
0 conflicts
0x168b8892…f447
0x34b655…2a6f
2 touches
0 conflicts
0x2c93d908…f150
0x34b655…2a6f
2 touches
0 conflicts
0x32b2548c…4105
0x34b655…2a6f
2 touches
0 conflicts
0x366a19b0…f065
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
0xca841faae5…71486a
Audit this contract →
← previous block
·
next block →
recent activity