pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#100,731,807
← previous block
next block →
recent activity
Analyzing
Block #100,731,807
13 transactions · 10 stateful · 2026-08-31 10:26:43 UTC
Parallelism
85
/100
Blocked
30
%
Avg conflicts / tx
0.23
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#100,731,807
· 13 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
updatePrices
#2
0xab083028
· blocks 1
#3
0x5acec890
· blocks 1
#5
0x59558d29
#6
0x1db5da08
#7
withdraw
#8
supply
· blocks 1
#10
setData
#11
execFwdPositionOpsV2
#4
0x928e4afa
#9
supply
#12
0xc7068c7b
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
2
w0
3
w0
4
w1
8
w0
9
w1
12
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xaf831072…51d5
0x69a5f9…2fef
4 touches
1 conflict
0xaf831072…51d6
0x69a5f9…2fef
4 touches
1 conflict
0xaf831072…51dc
0x69a5f9…2fef
4 touches
1 conflict
0x2ef1d89b…196d
0x754704…b603
4 touches
1 conflict
0x00000000…003d
0x851145…3f07
4 touches
1 conflict
0xca841faa…486a
0x34b655…2a6f
4 touches
1 conflict
0x00000000…0036
0x35a73b…6042
4 touches
1 conflict
0x5e8223c2…c242
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:
0x69a5f9ad…102fef
1 conflict on slot
0xaf831072f6…c551d5
Audit this contract →
← previous block
·
next block →
recent activity