pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#98,729,476
← previous block
next block →
recent activity
Analyzing
Block #98,729,476
11 transactions · 11 stateful · 2026-08-24 10:05:17 UTC
Parallelism
73
/100
Blocked
36
%
Avg conflicts / tx
0.36
Longest chain
3
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#98,729,476
· 11 txs across 3 waves · depth 3
parallel ↔ serial
wave
w0
wave
w1
wave
w2
#0
syscallReward
#1
0x41a8f47c
· blocks 2
#2
setData
#3
execOrders
#6
0xab083028
· blocks 1
#9
0x59558d29
#10
execFwdPositionOpsV2
#4
0xab083028
· blocks 1
#7
0x8263f5d9
#8
updatePrices
#5
0x32d01e04
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
1
w0
4
w1
5
w2
6
w0
7
w1
8
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…003d
0x40c49f…2af0
4 touches
1 conflict
0x3f81bcfb…2905
0x40c49f…2af0
4 touches
1 conflict
0x00000000…0002
0xbb3f3c…e046
4 touches
1 conflict
0xb64473b0…0d6f
0xc8689a…ee79
4 touches
1 conflict
0xbb97db90…4c93
0xc8689a…ee79
4 touches
1 conflict
0x10a81eed…c249
0x340143…768f
2 touches
0 conflicts
0x3c051be2…ba61
0x40c49f…2af0
2 touches
0 conflicts
0x00000000…0000
0x5d98f1…8bb2
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