pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#88,080,874
← previous block
next block →
recent activity
Analyzing
Block #88,080,874
12 transactions · 11 stateful · 2026-07-16 06:56:51 UTC
Parallelism
83
/100
Blocked
27
%
Avg conflicts / tx
0.25
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#88,080,874
· 12 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
0x39ecce49
· blocks 1
#3
0xab083028
· blocks 1
#5
updateDataFeedsValuesPartial
#6
updateDataFeedsValuesPartial
#7
execFwdPositionOps
· blocks 1
#9
executeBatch
#10
forward
#11
setData
#2
0x39ecce49
#4
0x6ad2e98b
#8
execFwdPositionOps
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
1
w0
2
w1
3
w0
4
w1
7
w0
8
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xcb9362f8…32bb
0xe4f6e7…9657
4 touches
1 conflict
0x00000000…0000
0x019883…2a9a
4 touches
1 conflict
0x00000000…0002
0x019883…2a9a
4 touches
1 conflict
0x00000000…0003
0x019883…2a9a
4 touches
1 conflict
0x724cd9ff…6684
0x0cc9b2…7777
4 touches
1 conflict
0x99a3a7c1…1e2b
0x0cc9b2…7777
4 touches
1 conflict
0x00000000…0008
0x0ea966…0742
4 touches
1 conflict
0x889d5e90…929a
0x2a68ba…90c5
4 touches
1 conflict
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:
0xe4f6e757…919657
1 conflict on slot
0xcb9362f812…f032bb
Audit this contract →
← previous block
·
next block →
recent activity