pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#104,197,615
← previous block
next block →
recent activity
Analyzing
Block #104,197,615
14 transactions · 13 stateful · 2026-09-12 13:59:20 UTC
Parallelism
71
/100
Blocked
23
%
Avg conflicts / tx
0.43
Longest chain
4
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#104,197,615
· 14 txs across 4 waves · depth 4
parallel ↔ serial
wave
w0
wave
w1
wave
w2
wave
w3
#0
syscallReward
#1
0x6aa55abb
#2
0xab083028
#3
0xab083028
#4
updatePrices
· blocks 3
#8
0x3e2e8792
#9
0x59558d29
#10
setData
#11
execFwdPositionOpsV2
#12
0xed82b078
#13
execOrders
#5
updatePrices
· blocks 2
#6
updatePrices
· blocks 1
#7
updatePrices
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
4
w0
5
w1
6
w2
7
w3
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…0002
0xf5b5f7…6d70
8 touches
6 conflicts
0x09000000…0007
0x000000…1000
2 touches
0 conflicts
0x0b000000…0002
0x000000…1000
2 touches
0 conflicts
0x09106a95…1467
0x33176b…e078
2 touches
0 conflicts
0x00000000…00c9
0x34b655…2a6f
2 touches
0 conflicts
0x010e79e9…95e4
0x34b655…2a6f
2 touches
0 conflicts
0x1244b105…8e9b
0x34b655…2a6f
2 touches
0 conflicts
0x168f7615…a8dd
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:
0xf5b5f7f8…a36d70
6 conflicts on slot
0x0000000000…000002
Audit this contract →
← previous block
·
next block →
recent activity