pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#98,735,537
← previous block
next block →
recent activity
Analyzing
Block #98,735,537
8 transactions · 8 stateful · 2026-08-24 10:35:46 UTC
Parallelism
75
/100
Blocked
13
%
Avg conflicts / tx
0.13
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#98,735,537
· 8 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
updatePrices
#2
0x59558d29
#3
aggregate3
#4
execFwdPositionOpsV2
· blocks 1
#6
updateTemporalNumericValuesV1
#7
0x6a8c1efa
#5
execFwdPositionOpsV2
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
4
w0
5
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xc824469a…6425
0x34b655…2a6f
4 touches
1 conflict
0xd2a24d67…eb6d
0x34b655…2a6f
4 touches
1 conflict
0xe8f57e05…3583
0x34b655…2a6f
4 touches
1 conflict
0xa6d40b7f…2969
0x34b655…2a6f
4 touches
1 conflict
0x00000000…0004
0x2d989e…0888
2 touches
0 conflicts
0x206f4379…e08a
0x34b655…2a6f
2 touches
0 conflicts
0x5e782d17…5317
0x34b655…2a6f
2 touches
0 conflicts
0x00000000…0004
0x46ea6f…1291
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:
Perpl
1 conflict on slot
0xc824469a90…af6425
Audit this contract →
← previous block
·
next block →
recent activity