pev
.
→
showcase
new
graph
analytics
docs
feedback
offline
by Silk Nodes
pev
/
block
/
#89,680,729
← previous block
next block →
recent activity
Analyzing
Block #89,680,729
11 transactions · 10 stateful · 2026-07-23 16:37:04 UTC
Parallelism
82
/100
Blocked
10
%
Avg conflicts / tx
0.09
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#89,680,729
· 11 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
exactOutputSingle
#2
updatePrices
#3
0x5a5d9a99
#4
0x5a5d9a99
#5
0x0f6795d9
· blocks 1
#6
updateDataFeedsValuesPartial
#7
updateDataFeedsValuesPartial
#9
0x39435dac
#10
setData
#8
0x0f6795d9
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
5
w0
8
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x310afe2c…83e1
0x34b655…2a6f
4 touches
1 conflict
0x09000000…0007
0x000000…1000
2 touches
0 conflicts
0x0b000000…0002
0x000000…1000
2 touches
0 conflicts
0x18aed20c…48f3
0x000000…012a
2 touches
0 conflicts
0x4245e4e8…096e
0x000000…012a
2 touches
0 conflicts
0x363a4317…87d2
0x34b655…2a6f
2 touches
0 conflicts
0x6b2ba712…0214
0x34b655…2a6f
2 touches
0 conflicts
0xaa48195d…ffee
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:
Perpl
1 conflict on slot
0x310afe2cd5…d683e1
Audit this contract →
← previous block
·
next block →
recent activity