pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#90,574,171
← previous block
next block →
recent activity
Analyzing
Block #90,574,171
10 transactions · 7 stateful · 2026-07-26 19:54:40 UTC
Parallelism
80
/100
Blocked
29
%
Avg conflicts / tx
0.2
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#90,574,171
· 10 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
0x0c7abd22
· blocks 1
#2
0x5739cb46
#4
0x6c05cd2b
#5
0x5a5d9a99
#6
updateDataFeedsValuesPartial
#7
execFwdPositionOps
· blocks 1
#9
setData
#3
0x6c05cd2b
#8
execFwdPositionOps
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
1
w0
3
w1
7
w0
8
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…0000
0x023eb9…b2b4
4 touches
1 conflict
0x00000000…0002
0x023eb9…b2b4
4 touches
1 conflict
0x00000000…0004
0x023eb9…b2b4
4 touches
1 conflict
0x00000000…000c
0x023eb9…b2b4
4 touches
1 conflict
0x28ad10b2…8b95
0x34b655…2a6f
4 touches
1 conflict
0x66bdb4c2…7ea6
0x34b655…2a6f
4 touches
1 conflict
0xc824469a…6425
0x34b655…2a6f
4 touches
1 conflict
0x11c3ab2d…cd65
0x3bd359…433a
4 touches
1 conflict
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:
0x023eb927…59b2b4
1 conflict on slot
0x0000000000…000000
Audit this contract →
← previous block
·
next block →
recent activity