pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#94,793,433
← previous block
next block →
recent activity
Analyzing
Block #94,793,433
12 transactions · 11 stateful · 2026-08-10 13:59:57 UTC
Parallelism
83
/100
Blocked
9
%
Avg conflicts / tx
0.08
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#94,793,433
· 12 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
execOrders
#2
updateDataFeedsValuesPartial
#3
0xeb282f7f
#4
execFwdPositionOps
· blocks 1
#6
execFwdPositionOps
#7
batchUpdate
#8
0x6a79d9d5
#9
transfer
#10
setData
#11
execOrders
#5
execFwdPositionOps
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
4
w0
5
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xdba3b90b…02bd
0x34b655…2a6f
4 touches
1 conflict
0x07b5dc27…d54c
0x34b655…2a6f
4 touches
1 conflict
0x4f4bdabd…ffba
0x34b655…2a6f
4 touches
1 conflict
0xa57576bb…e01f
0x34b655…2a6f
4 touches
1 conflict
0x0a2131b3…455e
0x34b655…2a6f
2 touches
0 conflicts
0x27cc7ce7…890d
0x34b655…2a6f
2 touches
0 conflicts
0x29c28125…fa31
0x34b655…2a6f
2 touches
0 conflicts
0x29eb4d5c…a77c
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
0xdba3b90b1b…dc02bd
Audit this contract →
← previous block
·
next block →
recent activity