pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#92,338,677
← previous block
next block →
recent activity
Analyzing
Block #92,338,677
11 transactions · 10 stateful · 2026-08-01 23:54:15 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
#92,338,677
· 11 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
0xab083028
#2
updateDataFeedsValuesPartial
#3
updateDataFeedsValuesPartial
#4
updateDataFeedsValuesPartial
#5
0x0f6795d9
#6
0x39435dac
#7
setData
#8
0x39435dac
· blocks 1
#10
updatePrices
#9
0x39435dac
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
0xf5aef04f…989e
0x34b655…2a6f
4 touches
1 conflict
0xd3ee14dc…7d81
0x34b655…2a6f
4 touches
1 conflict
0xd98b3c10…67b8
0x34b655…2a6f
4 touches
1 conflict
0xe99ebc4d…22f9
0x34b655…2a6f
4 touches
1 conflict
0x00ebed49…1e8f
0x34b655…2a6f
4 touches
1 conflict
0x083ff337…401b
0x34b655…2a6f
4 touches
1 conflict
0x2979e2dd…335e
0x34b655…2a6f
4 touches
1 conflict
0x36738a34…f160
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:
Perpl
1 conflict on slot
0xf5aef04f0a…b8989e
Audit this contract →
← previous block
·
next block →
recent activity