pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#106,367,496
← previous block
next block →
recent activity
Analyzing
Block #106,367,496
11 transactions · 10 stateful · 2026-09-20 04:26:35 UTC
Parallelism
73
/100
Blocked
20
%
Avg conflicts / tx
0.18
Longest chain
3
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#106,367,496
· 11 txs across 3 waves · depth 3
parallel ↔ serial
wave
w0
wave
w1
wave
w2
#0
syscallReward
#1
updatePrices
#2
0x5acec890
· blocks 1
#4
0x59558d29
#5
0x59558d29
#6
pet
#7
setData
#8
0x57368ddf
#9
0x6aaf607d
#3
0x5acec890
· blocks 1
#10
execOrders
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
2
w0
3
w1
10
w2
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xca841faa…486a
0x34b655…2a6f
4 touches
1 conflict
0xac2a0273…721b
0x34b655…2a6f
4 touches
1 conflict
0x0b000000…0002
0x000000…1000
2 touches
0 conflicts
0x131543ca…09ba
0x34b655…2a6f
2 touches
0 conflicts
0x22db2187…cb6b
0x34b655…2a6f
2 touches
0 conflicts
0x455a4eac…56c3
0x34b655…2a6f
2 touches
0 conflicts
0x57e5abc1…286f
0x34b655…2a6f
2 touches
0 conflicts
0x75fa2600…a957
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