pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#92,432,152
← previous block
next block →
recent activity
Analyzing
Block #92,432,152
10 transactions · 9 stateful · 2026-08-02 07:44:18 UTC
Parallelism
80
/100
Blocked
11
%
Avg conflicts / tx
0.2
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#92,432,152
· 10 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
0xab083028
#2
0x5acec890
· blocks 1
#3
0x0f6795d9
· blocks 1
#4
updateDataFeedsValuesPartial
#5
executeBatch
#6
0x39435dac
#8
setData
#9
0x59558d29
#7
0x0f6795d9
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
2
w0
3
w0
7
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xc824469a…6425
0x34b655…2a6f
4 touches
1 conflict
0xa3a621f8…75a2
0x34b655…2a6f
4 touches
1 conflict
0xac2a0273…721b
0x34b655…2a6f
4 touches
1 conflict
0xb3b996db…44af
0x34b655…2a6f
4 touches
1 conflict
0x154f65cf…14d6
0x34b655…2a6f
2 touches
0 conflicts
0x19fb7d60…da48
0x34b655…2a6f
2 touches
0 conflicts
0x1c796c6b…064e
0x34b655…2a6f
2 touches
0 conflicts
0x7cb2f3fa…4836
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
0xc824469a90…af6425
Audit this contract →
← previous block
·
next block →
recent activity