pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#91,409,360
← previous block
next block →
recent activity
Analyzing
Block #91,409,360
10 transactions · 7 stateful · 2026-07-29 17:58:38 UTC
Parallelism
80
/100
Blocked
14
%
Avg conflicts / tx
0.1
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#91,409,360
· 10 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
0xab083028
#2
updateDataFeedsValuesPartial
#3
0x0f6795d9
#4
0x0f6795d9
· blocks 1
#6
0x6a6a3fc6
#7
0xe0acae…824e
#8
0x9d7fb3…0cbf
#9
setData
#5
0x0f6795d9
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
0x85bfd0af…ce96
0x34b655…2a6f
4 touches
1 conflict
0xc824469a…6425
0x34b655…2a6f
4 touches
1 conflict
0x482471ad…122f
0x34b655…2a6f
4 touches
1 conflict
0x00000000…003d
0x065c9d…c394
2 touches
0 conflicts
0x116c6b2f…b15d
0x065c9d…c394
2 touches
0 conflicts
0x66c21f54…af0e
0x065c9d…c394
2 touches
0 conflicts
0xcbdccf41…ab3d
0x065c9d…c394
2 touches
0 conflicts
0xf0e2fe06…4741
0x065c9d…c394
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
0x85bfd0afba…f5ce96
Audit this contract →
← previous block
·
next block →
recent activity