pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#90,557,889
← previous block
next block →
recent activity
Analyzing
Block #90,557,889
9 transactions · 8 stateful · 2026-07-26 18:32:47 UTC
Parallelism
78
/100
Blocked
25
%
Avg conflicts / tx
0.22
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#90,557,889
· 9 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
0xab083028
#2
0x5a5d9a99
#3
updateDataFeedsValuesPartial
#4
execFwdPositionOps
· blocks 1
#5
0x29eed2d3
· blocks 1
#8
setData
#6
0x29eed2d3
#7
execFwdPositionOps
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
4
w0
5
w0
6
w1
7
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x5311f864…0984
0x754704…b603
4 touches
1 conflict
0x746b3fc2…0b34
0x34b655…2a6f
4 touches
1 conflict
0x889d5e90…929a
0x2a68ba…90c5
2 touches
0 conflicts
0x09f6bcb7…e9df
0x34b655…2a6f
2 touches
0 conflicts
0x1bf8d2af…d140
0x34b655…2a6f
2 touches
0 conflicts
0x6fe7d366…78ff
0x34b655…2a6f
2 touches
0 conflicts
0x78860c4f…cade
0x34b655…2a6f
2 touches
0 conflicts
0x921a58d1…db22
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:
USDC (USDC)
1 conflict on slot
0x5311f86450…380984
Audit this contract →
← previous block
·
next block →
recent activity