pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#104,704,669
← previous block
next block →
recent activity
Analyzing
Block #104,704,669
13 transactions · 11 stateful · 2026-09-14 08:52:49 UTC
Parallelism
85
/100
Blocked
27
%
Avg conflicts / tx
0.23
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#104,704,669
· 13 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
0x6aa7b5e5
#2
updatePrices
· blocks 1
#4
updatePrices
#5
0xab083028
· blocks 1
#6
0x59558d29
· blocks 1
#8
executeBatch
#10
forward
#11
execFwdPositionOpsV2
#12
0x6aa7b5e5
#3
updatePrices
#7
0x59558d29
#9
0xed82b078
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
2
w0
3
w1
5
w0
6
w0
7
w1
9
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…0002
0xf5b5f7…6d70
4 touches
1 conflict
0x00000000…003d
0x065c9d…c394
4 touches
1 conflict
0x52e69143…95ad
0x065c9d…c394
4 touches
1 conflict
0x00000000…004b
0x80c745…7210
4 touches
1 conflict
0x3d93f172…85ef
0x065c9d…c394
3 touches
1 conflict
0xa9530be5…2fce
0x065c9d…c394
3 touches
1 conflict
0x66fe6ebb…5731
0x065c9d…c394
3 touches
1 conflict
0x09000000…0001
0x000000…1000
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