pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#94,234,220
← previous block
next block →
recent activity
Analyzing
Block #94,234,220
11 transactions · 9 stateful · 2026-08-08 14:54:32 UTC
Parallelism
82
/100
Blocked
11
%
Avg conflicts / tx
0.09
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#94,234,220
· 11 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
0xe33905c2
#2
execFwdPositionOps
#3
execFwdPositionOps
· blocks 1
#4
execFwdPositionOps
#5
resolve
#7
updateDataFeedsValuesPartial
#8
setData
#9
execOrders
#10
execOrders
#6
execFwdPositionOps
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
3
w0
6
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x66bdb4c2…7ea6
0x34b655…2a6f
4 touches
1 conflict
0xc824469a…6425
0x34b655…2a6f
4 touches
1 conflict
0x0b000000…0002
0x000000…1000
2 touches
0 conflicts
0x05286dbb…4517
0x34b655…2a6f
2 touches
0 conflicts
0x2bea6eae…9f7b
0x34b655…2a6f
2 touches
0 conflicts
0x3476cbe2…496b
0x34b655…2a6f
2 touches
0 conflicts
0x3eadccfc…4e8e
0x34b655…2a6f
2 touches
0 conflicts
0x4069c511…21c8
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
0x66bdb4c268…a97ea6
Audit this contract →
← previous block
·
next block →
recent activity