pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#92,202,120
← previous block
next block →
recent activity
Analyzing
Block #92,202,120
12 transactions · 10 stateful · 2026-08-01 12:27:27 UTC
Parallelism
83
/100
Blocked
10
%
Avg conflicts / tx
0.08
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#92,202,120
· 12 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
updatePrices
#2
updateDataFeedsValuesPartial
#3
fulfillWithERC20
#4
0x3f5c179b
#5
0x39435dac
#6
0x39435dac
#7
0x0f6795d9
· blocks 1
#9
updateDataFeedsValuesPartial
#10
0x6a6de6a7
#11
setData
#8
0x0f6795d9
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
7
w0
8
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x66bdb4c2…7ea6
0x34b655…2a6f
4 touches
1 conflict
0xc824469a…6425
0x34b655…2a6f
4 touches
1 conflict
0x0b000000…0002
0x000000…1000
2 touches
0 conflicts
0x00000000…0004
0x081393…20b3
2 touches
0 conflicts
0x8ee994de…02b2
0x081393…20b3
2 touches
0 conflicts
0xbb371eab…3efc
0x081393…20b3
2 touches
0 conflicts
0x8e485ef0…8a8a
0x3bd359…433a
2 touches
0 conflicts
0xbfe7fd3a…3168
0x3bd359…433a
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
0x66bdb4c268…a97ea6
Audit this contract →
← previous block
·
next block →
recent activity