pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#94,477,406
← previous block
next block →
recent activity
Analyzing
Block #94,477,406
11 transactions · 7 stateful · 2026-08-09 11:28:57 UTC
Parallelism
82
/100
Blocked
14
%
Avg conflicts / tx
0.18
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#94,477,406
· 11 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
0x0c7abd22
#2
0x39435dac
#3
0x39435dac
#4
0x0f6795d9
· blocks 1
#5
0x0f6795d9
· blocks 1
#7
0xed82b078
#8
updateDataFeedsValuesPartial
#9
setData
#10
withdraw
#6
0x0f6795d9
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
4
w0
5
w0
6
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xc824469a…6425
0x34b655…2a6f
4 touches
1 conflict
0x66bdb4c2…7ea6
0x34b655…2a6f
4 touches
1 conflict
0x0b000000…0002
0x000000…1000
2 touches
0 conflicts
0x1d0a04dd…b892
0x34b655…2a6f
2 touches
0 conflicts
0x34d32294…d7b3
0x34b655…2a6f
2 touches
0 conflicts
0x3942bfcd…e059
0x34b655…2a6f
2 touches
0 conflicts
0x68a6a4e5…e631
0x34b655…2a6f
2 touches
0 conflicts
0x70a7b5d6…fe0e
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
1 conflict on slot
0xc824469a90…af6425
Audit this contract →
← previous block
·
next block →
recent activity