pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#90,978,578
← previous block
next block →
recent activity
Analyzing
Block #90,978,578
7 transactions · 7 stateful · 2026-07-28 05:49:15 UTC
Parallelism
71
/100
Blocked
14
%
Avg conflicts / tx
0.14
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#90,978,578
· 7 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
0x0f6795d9
· blocks 1
#2
updateDataFeedsValuesPartial
#3
0xed82b078
#4
setData
#6
0xc7e3ec2c
#5
0x39435dac
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
1
w0
5
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x5fe7e126…6dd2
0x34b655…2a6f
4 touches
1 conflict
0x99a020e0…04e2
0x34b655…2a6f
4 touches
1 conflict
0xab92d92c…c8bf
0x34b655…2a6f
4 touches
1 conflict
0x0733be30…112f
0x34b655…2a6f
2 touches
0 conflicts
0x0a02029e…5198
0x34b655…2a6f
2 touches
0 conflicts
0x0bd95eb4…e562
0x34b655…2a6f
2 touches
0 conflicts
0x10981d9e…6ebc
0x34b655…2a6f
2 touches
0 conflicts
0x151a39c9…e8e2
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
0x5fe7e1267e…896dd2
Audit this contract →
← previous block
·
next block →
recent activity