pev
.
→
showcase
new
graph
analytics
docs
feedback
offline
by Silk Nodes
pev
/
block
/
#89,750,656
← previous block
next block →
recent activity
Analyzing
Block #89,750,656
11 transactions · 11 stateful · 2026-07-23 22:30:02 UTC
Parallelism
73
/100
Blocked
27
%
Avg conflicts / tx
0.36
Longest chain
3
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#89,750,656
· 11 txs across 3 waves · depth 3
parallel ↔ serial
wave
w0
wave
w1
wave
w2
#0
syscallReward
#1
0x0f6795d9
· blocks 1
#2
0x0f6795d9
#3
forward
#5
updateDataFeedsValuesPartial
#6
0x6a629662
#7
transfer
· blocks 2
#10
setData
#4
0x39435dac
#8
transfer
· blocks 1
#9
transfer
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
1
w0
4
w1
7
w0
8
w1
9
w2
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x42041fec…bd86
0x754704…b603
6 touches
3 conflicts
0xbb322930…ace5
0x34b655…2a6f
4 touches
1 conflict
0x482471ad…122f
0x34b655…2a6f
4 touches
1 conflict
0x0110331c…b891
0x34b655…2a6f
2 touches
0 conflicts
0x43996a49…31e2
0x34b655…2a6f
2 touches
0 conflicts
0x502b445c…c1e5
0x34b655…2a6f
2 touches
0 conflicts
0x6baa6e8f…9e68
0x34b655…2a6f
2 touches
0 conflicts
0x7062dc95…8b16
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)
3 conflicts on slot
0x42041feca2…afbd86
Audit this contract →
← previous block
·
next block →
recent activity