pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#99,171,503
← previous block
next block →
recent activity
Analyzing
Block #99,171,503
9 transactions · 9 stateful · 2026-08-25 23:16:12 UTC
Parallelism
67
/100
Blocked
22
%
Avg conflicts / tx
0.33
Longest chain
3
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#99,171,503
· 9 txs across 3 waves · depth 3
parallel ↔ serial
wave
w0
wave
w1
wave
w2
#0
syscallReward
#1
0xab083028
#2
0x0c7abd22
#3
updateDataFeedsValuesPartial
#4
execOrders
· blocks 2
#7
0x6a8e22b3
#8
setData
#5
execOrders
· blocks 1
#6
execFwdPositionOpsV2
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
4
w0
5
w1
6
w2
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xaa468fc4…194a
0x34b655…2a6f
6 touches
3 conflicts
0x9d22c394…c125
0x34b655…2a6f
6 touches
3 conflicts
0xecd87a39…d9c5
0x34b655…2a6f
4 touches
1 conflict
0x078e7aa7…992d
0x34b655…2a6f
4 touches
1 conflict
0x232b0b19…d946
0x34b655…2a6f
4 touches
1 conflict
0x310a7246…2dcb
0x34b655…2a6f
4 touches
1 conflict
0xa21c9a17…c000
0x34b655…2a6f
4 touches
1 conflict
0x61b2753d…4ce6
0x34b655…2a6f
4 touches
1 conflict
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
3 conflicts on slot
0xaa468fc431…32194a
Audit this contract →
← previous block
·
next block →
recent activity