pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#94,288,549
← previous block
next block →
recent activity
Analyzing
Block #94,288,549
12 transactions · 11 stateful · 2026-08-08 19:29:50 UTC
Parallelism
83
/100
Blocked
18
%
Avg conflicts / tx
0.17
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#94,288,549
· 12 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
0x0c7abd22
#2
execOrder
#3
execOrders
#4
0x928e4afa
· blocks 1
#5
updatePrices
#6
execFwdPositionOps
· blocks 1
#8
executeBatch
#9
updateDataFeedsValuesPartial
#10
setData
#7
execFwdPositionOps
#11
execOrders
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
4
w0
6
w0
7
w1
11
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x1d5181ef…7074
0x34b655…2a6f
4 touches
1 conflict
0x21ef0807…d889
0x34b655…2a6f
4 touches
1 conflict
0x66bdb4c2…7ea6
0x34b655…2a6f
4 touches
1 conflict
0x8ce19e5c…e818
0x34b655…2a6f
4 touches
1 conflict
0xb416438e…796a
0x34b655…2a6f
4 touches
1 conflict
0xb5a3b1be…8122
0x34b655…2a6f
4 touches
1 conflict
0xc824469a…6425
0x34b655…2a6f
4 touches
1 conflict
0xea02471d…1542
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
0x1d5181ef0a…457074
Audit this contract →
← previous block
·
next block →
recent activity