pev
.
→
showcase
new
graph
analytics
docs
feedback
offline
by Silk Nodes
pev
/
block
/
#89,737,108
← previous block
next block →
recent activity
Analyzing
Block #89,737,108
13 transactions · 13 stateful · 2026-07-23 21:21:33 UTC
Parallelism
85
/100
Blocked
8
%
Avg conflicts / tx
0.08
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#89,737,108
· 13 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
0xab083028
#2
0x5a5d9a99
#3
0x5a5d9a99
#4
updateDataFeedsValuesPartial
#5
0x0f6795d9
#6
0x0f6795d9
#7
metacall
#8
0xce1e7030
· blocks 1
#10
0x6a628654
#11
setData
#12
0x39435dac
#9
0xce1e7030
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
8
w0
9
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xa1087a5c…66c4
0x754704…b603
4 touches
1 conflict
0xddc22bc2…7f7a
0x754704…b603
4 touches
1 conflict
0x392a02b5…0019
0x81a224…7777
4 touches
1 conflict
0x4c770fe0…b972
0x3bd359…433a
4 touches
1 conflict
0x00000000…0000
0x714a26…182d
4 touches
1 conflict
0x00000000…0003
0x714a26…182d
4 touches
1 conflict
0x29856edf…841b
0x34b655…2a6f
2 touches
0 conflicts
0x5eb187dd…b1d6
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
0xa1087a5ca6…0a66c4
Audit this contract →
← previous block
·
next block →
recent activity