pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#101,323,201
← previous block
next block →
recent activity
Analyzing
Block #101,323,201
11 transactions · 11 stateful · 2026-09-02 12:02:36 UTC
Parallelism
82
/100
Blocked
18
%
Avg conflicts / tx
0.18
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#101,323,201
· 11 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
0x0c7abd22
· blocks 1
#2
updatePrices
#3
0xab083028
#5
0x8263f5d9
· blocks 1
#6
updateDataFeedsValuesPartial
#7
0x59558d29
#8
bet
#9
execFwdPositionOpsV2
#4
0xab083028
#10
0xc7068c7b
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
1
w0
4
w1
5
w0
10
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…003d
0x40c49f…2af0
4 touches
1 conflict
0x00000000…003d
0x065c9d…c394
4 touches
1 conflict
0x0b000000…0002
0x000000…1000
2 touches
0 conflicts
0x15aa9b8a…1c3d
0x065c9d…c394
2 touches
0 conflicts
0x4db094a9…366f
0x065c9d…c394
2 touches
0 conflicts
0x95523e2a…4c01
0x065c9d…c394
2 touches
0 conflicts
0xc777d65d…b120
0x065c9d…c394
2 touches
0 conflicts
0xf0adbe24…2baa
0x065c9d…c394
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:
0x40c49f17…d22af0
1 conflict on slot
0x0000000000…00003d
Audit this contract →
← previous block
·
next block →
recent activity