pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#94,739,620
← previous block
next block →
recent activity
Analyzing
Block #94,739,620
10 transactions · 10 stateful · 2026-08-10 09:28:14 UTC
Parallelism
80
/100
Blocked
10
%
Avg conflicts / tx
0.1
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#94,739,620
· 10 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
0x5acec890
#2
updateDataFeedsValuesPartial
#3
execFwdPositionOps
· blocks 1
#5
0x3f5c179b
#6
execFwdPositionOps
#7
0x6a799a26
#8
setData
#9
execOrders
#4
execFwdPositionOps
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
3
w0
4
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xaa4c25ab…a537
0x34b655…2a6f
4 touches
1 conflict
0xbcbf5d09…8bac
0x34b655…2a6f
4 touches
1 conflict
0xc824469a…6425
0x34b655…2a6f
4 touches
1 conflict
0x3315b0fc…ee37
0x34b655…2a6f
4 touches
1 conflict
0x7588493b…f7c3
0x34b655…2a6f
3 touches
1 conflict
0x4392cbcd…6a92
0x34b655…2a6f
2 touches
0 conflicts
0x4ae3b148…7ed2
0x34b655…2a6f
2 touches
0 conflicts
0x845ec8b0…c1af
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:
Perpl
1 conflict on slot
0xaa4c25abbe…eca537
Audit this contract →
← previous block
·
next block →
recent activity