pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#94,674,821
← previous block
next block →
recent activity
Analyzing
Block #94,674,821
14 transactions · 12 stateful · 2026-08-10 04:01:52 UTC
Parallelism
86
/100
Blocked
17
%
Avg conflicts / tx
0.14
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#94,674,821
· 14 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
0x0c7abd22
#2
0xab083028
#3
execOrders
· blocks 2
#4
execOrders
#6
updatePrices
#7
updateDataFeedsValuesPartial
#8
updateDataFeedsValuesPartial
#10
forward
#11
commit
#12
setData
#13
execOrders
#5
execOrders
#9
execFwdPositionOps
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
3
w0
5
w1
9
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xf3d10975…0d07
0x34b655…2a6f
4 touches
1 conflict
0xbde524f4…43bf
0x34b655…2a6f
4 touches
1 conflict
0xea02471d…1542
0x34b655…2a6f
4 touches
1 conflict
0x889d5e90…929a
0x2a68ba…90c5
2 touches
0 conflicts
0x1bf8d2af…d140
0x34b655…2a6f
2 touches
0 conflicts
0x1e2b2634…63f5
0x34b655…2a6f
2 touches
0 conflicts
0x3572f533…4b93
0x34b655…2a6f
2 touches
0 conflicts
0x37cb667b…2139
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
0xf3d10975b0…050d07
Audit this contract →
← previous block
·
next block →
recent activity