pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#91,242,730
← previous block
next block →
recent activity
Analyzing
Block #91,242,730
10 transactions · 9 stateful · 2026-07-29 03:59:01 UTC
Parallelism
80
/100
Blocked
11
%
Avg conflicts / tx
0.1
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#91,242,730
· 10 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
updateDataFeedsValuesPartial
#2
0x0f6795d9
#3
updatePosition
#4
0x3f5c179b
· blocks 1
#6
0x39435dac
#7
0x6a697afc
#8
setData
#9
0x39435dac
#5
batchUpdate
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
4
w0
5
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xcc1dfa1c…681c
0x40c49f…2af0
4 touches
1 conflict
0x00000000…003d
0x40c49f…2af0
4 touches
1 conflict
0x0b000000…0002
0x000000…1000
2 touches
0 conflicts
0x43fd3667…094b
0x34b655…2a6f
2 touches
0 conflicts
0x4aa7e8d1…4656
0x34b655…2a6f
2 touches
0 conflicts
0x6925548b…81cb
0x34b655…2a6f
2 touches
0 conflicts
0x6925548b…81cc
0x34b655…2a6f
2 touches
0 conflicts
0x737acb78…fce8
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:
0x40c49f17…d22af0
1 conflict on slot
0xcc1dfa1c7f…13681c
Audit this contract →
← previous block
·
next block →
recent activity