pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#94,227,909
← previous block
next block →
recent activity
Analyzing
Block #94,227,909
10 transactions · 8 stateful · 2026-08-08 14:22:24 UTC
Parallelism
80
/100
Blocked
13
%
Avg conflicts / tx
0.1
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#94,227,909
· 10 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
0x0c7abd22
#2
0x5acec890
· blocks 1
#3
0x5acec890
#4
0x39435dac
#5
updateDataFeedsValuesPartial
#6
updateDataFeedsValuesPartial
#7
0x0f6795d9
#9
setData
#8
0x0f6795d9
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
2
w0
8
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x5ab74544…e16c
0x34b655…2a6f
4 touches
1 conflict
0x61b1ca86…dac1
0x34b655…2a6f
4 touches
1 conflict
0x5502e1cc…3910
0x34b655…2a6f
4 touches
1 conflict
0xac2a0273…721b
0x34b655…2a6f
4 touches
1 conflict
0xff9e45bf…99a0
0x34b655…2a6f
4 touches
1 conflict
0x18de6e82…7ec0
0x34b655…2a6f
2 touches
0 conflicts
0x1e81a9a0…46aa
0x34b655…2a6f
2 touches
0 conflicts
0x2484cc15…5afc
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
0x5ab74544d2…d5e16c
Audit this contract →
← previous block
·
next block →
recent activity