pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#90,286,568
← previous block
next block →
recent activity
Analyzing
Block #90,286,568
9 transactions · 8 stateful · 2026-07-25 19:34:02 UTC
Parallelism
78
/100
Blocked
25
%
Avg conflicts / tx
0.22
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#90,286,568
· 9 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
0x0f6795d9
· blocks 1
#3
updateDataFeedsValuesPartial
#4
updateDataFeedsValuesPartial
#5
0x6a651022
#6
transfer
· blocks 1
#8
setData
#2
0x39435dac
#7
transfer
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
1
w0
2
w1
6
w0
7
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x03c38bff…f48f
0x34b655…2a6f
4 touches
1 conflict
0x42041fec…bd86
0x754704…b603
4 touches
1 conflict
0x0b000000…0002
0x000000…1000
2 touches
0 conflicts
0x045502c3…b241
0x34b655…2a6f
2 touches
0 conflicts
0x19c5bd01…7daf
0x34b655…2a6f
2 touches
0 conflicts
0x1de7f7ac…e239
0x34b655…2a6f
2 touches
0 conflicts
0x58a68b92…6a6e
0x34b655…2a6f
2 touches
0 conflicts
0x61e01cd0…b73e
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
0x03c38bff08…caf48f
Audit this contract →
← previous block
·
next block →
recent activity