pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#94,810,800
← previous block
next block →
recent activity
Analyzing
Block #94,810,800
10 transactions · 9 stateful · 2026-08-10 15:27:20 UTC
Parallelism
80
/100
Blocked
11
%
Avg conflicts / tx
0.1
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#94,810,800
· 10 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
execOrder
· blocks 1
#3
updateDataFeedsValuesPartial
#4
bet
#5
forward
#6
execFwdPositionOps
#7
execFwdPositionOps
#8
0x6a79ee4f
#9
setData
#2
execOrder
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
1
w0
2
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x734ee320…caae
0x34b655…2a6f
4 touches
1 conflict
0x09000000…0007
0x000000…1000
2 touches
0 conflicts
0x0b000000…0002
0x000000…1000
2 touches
0 conflicts
0x18c53a40…8bd0
0x34b655…2a6f
2 touches
0 conflicts
0x1d946063…ba90
0x34b655…2a6f
2 touches
0 conflicts
0x4dc6cd61…f674
0x34b655…2a6f
2 touches
0 conflicts
0x563bbb55…861a
0x34b655…2a6f
2 touches
0 conflicts
0x9b2d3bee…8eeb
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
0x734ee32053…cecaae
Audit this contract →
← previous block
·
next block →
recent activity