pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#94,470,081
← previous block
next block →
recent activity
Analyzing
Block #94,470,081
8 transactions · 7 stateful · 2026-08-09 10:52:04 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,470,081
· 8 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
updateDataFeedsValuesPartial
#2
execFwdPositionOps
#3
execFwdPositionOps
· blocks 1
#5
0x6a785c4c
#6
setData
#7
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
0xcc9de8a7…c1f5
0x34b655…2a6f
4 touches
1 conflict
0xe4af4c87…9964
0x34b655…2a6f
4 touches
1 conflict
0xed08ca1d…48bd
0x34b655…2a6f
4 touches
1 conflict
0x0a69ac58…4bde
0x34b655…2a6f
2 touches
0 conflicts
0x222733a8…8e7a
0x34b655…2a6f
2 touches
0 conflicts
0x222733a8…8e7b
0x34b655…2a6f
2 touches
0 conflicts
0x388a4c2f…9868
0x34b655…2a6f
2 touches
0 conflicts
0x441923dd…d1a6
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
0xcc9de8a772…27c1f5
Audit this contract →
← previous block
·
next block →
recent activity