pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#91,423,341
← previous block
next block →
recent activity
Analyzing
Block #91,423,341
10 transactions · 10 stateful · 2026-07-29 19:09:04 UTC
Parallelism
80
/100
Blocked
10
%
Avg conflicts / tx
0.1
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#91,423,341
· 10 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
updatePrices
· blocks 1
#3
updateDataFeedsValuesPartial
#4
0x0f6795d9
#5
0x29eed2d3
#6
forward
#7
0x0f6795d9
#8
setData
#9
approve
#2
updatePrices
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
1
w0
2
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…0002
0x48cba2…b48b
4 touches
1 conflict
0x09000000…0007
0x000000…1000
2 touches
0 conflicts
0x0b000000…0002
0x000000…1000
2 touches
0 conflicts
0x0f4fd7ed…38fa
0x34b655…2a6f
2 touches
0 conflicts
0x143556cd…07a5
0x34b655…2a6f
2 touches
0 conflicts
0x1bde9f7f…c070
0x34b655…2a6f
2 touches
0 conflicts
0x1ce74984…23fc
0x34b655…2a6f
2 touches
0 conflicts
0x1d351a9b…f2dd
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:
0x48cba278…e2b48b
1 conflict on slot
0x0000000000…000002
Audit this contract →
← previous block
·
next block →
recent activity