pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#90,772,217
← previous block
next block →
recent activity
Analyzing
Block #90,772,217
13 transactions · 10 stateful · 2026-07-27 12:30:58 UTC
Parallelism
85
/100
Blocked
10
%
Avg conflicts / tx
0.08
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#90,772,217
· 13 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
0xab083028
#2
handleOps
#3
0x4d8dc985
· blocks 1
#4
0x5bf9264c
#5
0x5bf9264c
#6
0x5a5d9a99
#8
0x0f6795d9
#9
updateDataFeedsValuesPartial
#10
executeBatch
#11
setData
#12
0xc7e3ec2c
#7
0x0f6795d9
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
3
w0
7
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xbfc5d23d…6ad7
0x34b655…2a6f
4 touches
1 conflict
0x09000000…0007
0x000000…1000
2 touches
0 conflicts
0x0b000000…0002
0x000000…1000
2 touches
0 conflicts
0xabb3e352…8140
0x000000…8ba3
2 touches
0 conflicts
0x0e2a90d5…867d
0x000000…a032
2 touches
0 conflicts
0xa56a84d2…0dcd
0x000000…a032
2 touches
0 conflicts
0x00000000…003d
0x065c9d…c394
2 touches
0 conflicts
0x0ddfdaf2…9e00
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
0xbfc5d23dd9…cd6ad7
Audit this contract →
← previous block
·
next block →
recent activity