pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#94,220,607
← previous block
next block →
recent activity
Analyzing
Block #94,220,607
8 transactions · 7 stateful · 2026-08-08 13:45:24 UTC
Parallelism
75
/100
Blocked
14
%
Avg conflicts / tx
0.13
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#94,220,607
· 8 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
0x0c7abd22
#2
updateDataFeedsValuesPartial
#3
updateDataFeedsValuesPartial
#4
execFwdPositionOps
· blocks 1
#6
execFwdPositionOps
#7
setData
#5
execFwdPositionOps
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
0xff28ee17…414e
0x34b655…2a6f
4 touches
1 conflict
0x14fe1598…d0ba
0x34b655…2a6f
4 touches
1 conflict
0x49b0842d…0a93
0x34b655…2a6f
4 touches
1 conflict
0x67d726f0…de26
0x34b655…2a6f
4 touches
1 conflict
0x68ebc41b…2b3d
0x34b655…2a6f
4 touches
1 conflict
0x737acb78…fce8
0x34b655…2a6f
4 touches
1 conflict
0x740353ff…95b0
0x34b655…2a6f
4 touches
1 conflict
0x77efb543…f7c2
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
1 conflict on slot
0xff28ee1740…f0414e
Audit this contract →
← previous block
·
next block →
recent activity