pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#94,056,212
← previous block
next block →
recent activity
Analyzing
Block #94,056,212
9 transactions · 8 stateful · 2026-08-07 23:54:36 UTC
Parallelism
78
/100
Blocked
13
%
Avg conflicts / tx
0.11
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#94,056,212
· 9 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
0xa96df62f
#2
0x222d4ad6
#3
execFwdPositionOps
· blocks 1
#5
execFwdPositionOps
#6
updateDataFeedsValuesPartial
#7
setData
#8
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
0xb3ca8fce…613e
0x34b655…2a6f
4 touches
1 conflict
0xb550abea…2729
0x34b655…2a6f
4 touches
1 conflict
0xc824469a…6425
0x34b655…2a6f
4 touches
1 conflict
0x015a89cc…7a96
0x34b655…2a6f
4 touches
1 conflict
0x09924b4d…d104
0x34b655…2a6f
4 touches
1 conflict
0x482471ad…122f
0x34b655…2a6f
4 touches
1 conflict
0x69411fb3…e36d
0x34b655…2a6f
4 touches
1 conflict
0xabba7bd6…8269
0x34b655…2a6f
4 touches
1 conflict
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
0xb3ca8fcee0…4d613e
Audit this contract →
← previous block
·
next block →
recent activity