pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#94,483,937
← previous block
next block →
recent activity
Analyzing
Block #94,483,937
9 transactions · 6 stateful · 2026-08-09 12:01:48 UTC
Parallelism
67
/100
Blocked
33
%
Avg conflicts / tx
0.33
Longest chain
3
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#94,483,937
· 9 txs across 3 waves · depth 3
parallel ↔ serial
wave
w0
wave
w1
wave
w2
#0
syscallReward
#1
execFwdPositionOps
· blocks 2
#4
0xc925b3a5
#5
updateDataFeedsValuesPartial
#6
setData
#7
0xe67d15…93bb
#8
0xc7e3ec2c
#2
execFwdPositionOps
· blocks 1
#3
execFwdPositionOps
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
1
w0
2
w1
3
w2
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xc824469a…6425
0x34b655…2a6f
6 touches
3 conflicts
0x43076802…d920
0x34b655…2a6f
4 touches
1 conflict
0xbcbf5d09…8bac
0x34b655…2a6f
4 touches
1 conflict
0xd44e517e…8d2f
0x34b655…2a6f
4 touches
1 conflict
0x261cbea7…e35d
0x34b655…2a6f
2 touches
0 conflicts
0x261cbea7…e35e
0x34b655…2a6f
2 touches
0 conflicts
0x3b3f6435…53a7
0x34b655…2a6f
2 touches
0 conflicts
0x657ef8e0…40dd
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
0xc824469a90…af6425
Audit this contract →
← previous block
·
next block →
recent activity