pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#94,278,673
← previous block
next block →
recent activity
Analyzing
Block #94,278,673
11 transactions · 11 stateful · 2026-08-08 18:39:54 UTC
Parallelism
82
/100
Blocked
18
%
Avg conflicts / tx
0.18
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#94,278,673
· 11 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
execOrders
· blocks 1
#3
0x5acec890
#4
execOrders
#5
execFwdPositionOps
· blocks 1
#6
updateDataFeedsValuesPartial
#7
updatePosition
#8
batchUpdate
#10
setData
#2
execOrders
#9
execFwdPositionOps
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
1
w0
2
w1
5
w0
9
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x05f129c9…ca9f
0x34b655…2a6f
4 touches
1 conflict
0x34a1ee7e…fb20
0x34b655…2a6f
4 touches
1 conflict
0x48315f67…c1a6
0x34b655…2a6f
4 touches
1 conflict
0x57ce341f…2f48
0x34b655…2a6f
4 touches
1 conflict
0x5e800a72…0189
0x34b655…2a6f
4 touches
1 conflict
0x737acb78…fce8
0x34b655…2a6f
4 touches
1 conflict
0x80fa9d80…b8d6
0x34b655…2a6f
4 touches
1 conflict
0xac2a0273…721b
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
0x05f129c9c7…57ca9f
Audit this contract →
← previous block
·
next block →
recent activity