pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#90,805,956
← previous block
next block →
recent activity
Analyzing
Block #90,805,956
10 transactions · 9 stateful · 2026-07-27 15:20:45 UTC
Parallelism
80
/100
Blocked
22
%
Avg conflicts / tx
0.2
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#90,805,956
· 10 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
execute
#2
0x5a5d9a99
· blocks 1
#3
0x0f6795d9
· blocks 1
#5
updateDataFeedsValuesPartial
#6
forward
#7
0x6a6777c5
#8
setData
#4
0x0f6795d9
#9
0x39435dac
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
2
w0
3
w0
4
w1
9
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xcdc1731c…b91a
0x34b655…2a6f
4 touches
1 conflict
0x19cbeea8…ecf3
0x34b655…2a6f
4 touches
1 conflict
0x0b000000…0002
0x000000…1000
2 touches
0 conflicts
0x0649b8e0…c704
0x34b655…2a6f
2 touches
0 conflicts
0x0cf9f3c8…ae89
0x34b655…2a6f
2 touches
0 conflicts
0x0dc62e18…08da
0x34b655…2a6f
2 touches
0 conflicts
0x0f82dba2…24d6
0x34b655…2a6f
2 touches
0 conflicts
0x160cf89e…1f72
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
0xcdc1731c6b…b6b91a
Audit this contract →
← previous block
·
next block →
recent activity