pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#94,760,645
← previous block
next block →
recent activity
Analyzing
Block #94,760,645
13 transactions · 11 stateful · 2026-08-10 11:15:02 UTC
Parallelism
92
/100
Blocked
0
%
Avg conflicts / tx
0
Longest chain
1
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#94,760,645
· 13 txs across 1 wave · depth 1
parallel ↔ serial
wave
w0
#0
syscallReward
#1
execute_route
#2
0x41a8f47c
#3
0x41a8f47c
#4
0x0c7abd22
#5
0xeb282f7f
#6
0x5acec890
#7
execFwdPositionOps
#8
execFwdPositionOps
#9
0xed82b078
#10
forward
#11
execFwdPositionOps
#12
setData
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
● no conflicts
every tx in this block runs in parallel
Hot storage slots
Contention
0x09000000…0001
0x000000…1000
2 touches
0 conflicts
0x09000000…0007
0x000000…1000
2 touches
0 conflicts
0x00a05b13…ce17
0x1efe02…37d6
2 touches
0 conflicts
0x889d5e90…929a
0x2a68ba…90c5
2 touches
0 conflicts
0x72c6bfb7…d5cf
0x5dd8f3…c69c
2 touches
0 conflicts
0xd421a518…8b5c
0x5dd8f3…c69c
2 touches
0 conflicts
0x0b552eae…fbd9
0x754704…b603
2 touches
0 conflicts
0x5f55f2c8…8f11
0x754704…b603
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.
← previous block
·
next block →
recent activity