pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#90,868,210
← previous block
next block →
recent activity
Analyzing
Block #90,868,210
10 transactions · 9 stateful · 2026-07-27 20:34:03 UTC
Parallelism
80
/100
Blocked
11
%
Avg conflicts / tx
0.1
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#90,868,210
· 10 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
execFwdPositionOps
#2
updateDataFeedsValuesPartial
#3
execFwdPositionOps
· blocks 1
#4
0x6a67c133
#5
0xe9316489
#6
setData
#8
execOrders
#9
0xc7e3ec2c
#7
execOrders
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
0x5c5238c6…f2dc
0x34b655…2a6f
4 touches
1 conflict
0x09000000…0007
0x000000…1000
2 touches
0 conflicts
0x09106a95…1467
0x33176b…e078
2 touches
0 conflicts
0x0b9fb562…9151
0x34b655…2a6f
2 touches
0 conflicts
0x3969618f…86d0
0x34b655…2a6f
2 touches
0 conflicts
0x58191830…04dd
0x34b655…2a6f
2 touches
0 conflicts
0x890a06f3…8539
0x34b655…2a6f
2 touches
0 conflicts
0xa4e9800f…4ab0
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
0x5c5238c656…aaf2dc
Audit this contract →
← previous block
·
next block →
recent activity