pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#94,858,136
← previous block
next block →
recent activity
Analyzing
Block #94,858,136
8 transactions · 7 stateful · 2026-08-10 19:25:28 UTC
Parallelism
63
/100
Blocked
29
%
Avg conflicts / tx
0.38
Longest chain
3
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#94,858,136
· 8 txs across 3 waves · depth 3
parallel ↔ serial
wave
w0
wave
w1
wave
w2
#0
syscallReward
#1
0xab083028
#2
execOrder
· blocks 2
#3
updateDataFeedsValuesPartial
#5
0x57368ddf
#7
0x6a7a2620
#4
execFwdPositionOps
· blocks 1
#6
execFwdPositionOps
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
2
w0
4
w1
6
w2
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xa1db0634…3c6c
0x34b655…2a6f
6 touches
3 conflicts
0xc824469a…6425
0x34b655…2a6f
4 touches
1 conflict
0x5655f5c3…6b75
0x34b655…2a6f
4 touches
1 conflict
0x889d5e90…929a
0x2a68ba…90c5
2 touches
0 conflicts
0x04994ed2…9032
0x34b655…2a6f
2 touches
0 conflicts
0x0865e7a7…5808
0x34b655…2a6f
2 touches
0 conflicts
0x0dd7d6d8…3700
0x34b655…2a6f
2 touches
0 conflicts
0x152f8e3d…3da0
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
3 conflicts on slot
0xa1db06340f…5c3c6c
Audit this contract →
← previous block
·
next block →
recent activity