pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#92,460,106
← previous block
next block →
recent activity
Analyzing
Block #92,460,106
8 transactions · 7 stateful · 2026-08-02 10:04:53 UTC
Parallelism
75
/100
Blocked
14
%
Avg conflicts / tx
0.13
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#92,460,106
· 8 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
updatePrices
#2
0x4d8dc985
· blocks 1
#3
updateDataFeedsValuesPartial
#4
updateDataFeedsValuesPartial
#5
setData
#7
0x59558d29
#6
0x0f6795d9
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
2
w0
6
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x7ce5b49a…237c
0x34b655…2a6f
4 touches
1 conflict
0x7b473fca…bdd8
0x34b655…2a6f
4 touches
1 conflict
0x09106a95…1467
0x33176b…e078
2 touches
0 conflicts
0xdbadf6b0…43b2
0x33176b…e078
2 touches
0 conflicts
0x18978822…2623
0x34b655…2a6f
2 touches
0 conflicts
0x21be2c2d…cb0b
0x34b655…2a6f
2 touches
0 conflicts
0x23a320fb…cbd7
0x34b655…2a6f
2 touches
0 conflicts
0x43e15ca4…039d
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
0x7ce5b49adf…16237c
Audit this contract →
← previous block
·
next block →
recent activity