pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#90,286,755
← previous block
next block →
recent activity
Analyzing
Block #90,286,755
11 transactions · 10 stateful · 2026-07-25 19:34:59 UTC
Parallelism
82
/100
Blocked
20
%
Avg conflicts / tx
0.18
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#90,286,755
· 11 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
0x0c7abd22
#2
0xab083028
#3
0x0f6795d9
· blocks 1
#5
0x1fe271b4
· blocks 1
#7
updateDataFeedsValuesPartial
#8
setData
#9
0x7294ed…892a
#10
0x39435dac
#4
0x0f6795d9
#6
claim
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
3
w0
4
w1
5
w0
6
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x55b4e430…44cb
0x754704…b603
4 touches
1 conflict
0x00000000…0006
0x0a2fbf…29b1
4 touches
1 conflict
0x00000000…00c9
0x34b655…2a6f
4 touches
1 conflict
0x33f7c11b…014f
0x34b655…2a6f
4 touches
1 conflict
0x34933aba…06e4
0x34b655…2a6f
4 touches
1 conflict
0x4954a433…820d
0x34b655…2a6f
4 touches
1 conflict
0xbcbf5d09…8bac
0x34b655…2a6f
4 touches
1 conflict
0xc824469a…641f
0x34b655…2a6f
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:
USDC (USDC)
1 conflict on slot
0x55b4e430de…d044cb
Audit this contract →
← previous block
·
next block →
recent activity