pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#92,446,400
← previous block
next block →
recent activity
Analyzing
Block #92,446,400
11 transactions · 9 stateful · 2026-08-02 08:55:57 UTC
Parallelism
82
/100
Blocked
22
%
Avg conflicts / tx
0.18
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#92,446,400
· 11 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
updatePrices
#2
0xa96df62f
#3
0x5bf9264c
#4
0x5bf9264c
#5
updateDataFeedsValuesPartial
#6
0x0f6795d9
· blocks 2
#9
setData
#10
0x59558d29
#7
0x0f6795d9
#8
0x0f6795d9
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
6
w0
7
w1
8
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x92385428…6941
0x34b655…2a6f
4 touches
1 conflict
0x954e62f9…0b7d
0x34b655…2a6f
4 touches
1 conflict
0xc824469a…6425
0x34b655…2a6f
4 touches
1 conflict
0xca3f7973…e7e7
0x34b655…2a6f
4 touches
1 conflict
0xca3f7973…e7e8
0x34b655…2a6f
4 touches
1 conflict
0xcc1b52d3…76b9
0x34b655…2a6f
4 touches
1 conflict
0x00000000…00c9
0x34b655…2a6f
4 touches
1 conflict
0x50e84e6c…287f
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
0x92385428ad…dc6941
Audit this contract →
← previous block
·
next block →
recent activity