pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#91,025,851
← previous block
next block →
recent activity
Analyzing
Block #91,025,851
12 transactions · 11 stateful · 2026-07-28 09:47:55 UTC
Parallelism
83
/100
Blocked
9
%
Avg conflicts / tx
0.08
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#91,025,851
· 12 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
updatePrices
#2
0x5a5d9a99
#3
0x0f6795d9
· blocks 1
#5
updateDataFeedsValuesPartial
#6
updateDataFeedsValuesPartial
#7
0x0f6795d9
#8
0x6a687b43
#9
setData
#10
0x39435dac
#11
0xc7e3ec2c
#4
0x0f6795d9
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
3
w0
4
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xacd1b162…bee6
0x34b655…2a6f
4 touches
1 conflict
0x09000000…0007
0x000000…1000
2 touches
0 conflicts
0x0b000000…0002
0x000000…1000
2 touches
0 conflicts
0x00000000…00c9
0x34b655…2a6f
2 touches
0 conflicts
0x12094652…111b
0x34b655…2a6f
2 touches
0 conflicts
0x143ef3f5…62b1
0x34b655…2a6f
2 touches
0 conflicts
0x299c0f04…09cf
0x34b655…2a6f
2 touches
0 conflicts
0x2d3930d3…c9b8
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
0xacd1b16256…3bbee6
Audit this contract →
← previous block
·
next block →
recent activity