pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#89,599,800
← previous block
next block →
recent activity
Analyzing
Block #89,599,800
13 transactions · 11 stateful · 2026-07-23 08:14:45 UTC
Parallelism
85
/100
Blocked
9
%
Avg conflicts / tx
0.08
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#89,599,800
· 13 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
exec
#2
0x5a5d9a99
#3
0x5a5d9a99
#4
0x5a5d9a99
#5
updateDataFeedsValuesPartial
#6
execFwdPositionOps
#7
execFwdPositionOps
#8
0xc925b3a5
· blocks 1
#10
execFwdPositionOps
#11
approve
#12
setData
#9
claim
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
8
w0
9
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x23c1447b…456b
0x0a2fbf…29b1
4 touches
1 conflict
0x00000000…0006
0x0a2fbf…29b1
4 touches
1 conflict
0x55b4e430…44cb
0x754704…b603
4 touches
1 conflict
0x00000000…0002
0x0aa9bd…5d57
2 touches
0 conflicts
0x00000000…0004
0x0aa9bd…5d57
2 touches
0 conflicts
0x00000000…000c
0x0aa9bd…5d57
2 touches
0 conflicts
0x0d2e1791…c1dd
0x34b655…2a6f
2 touches
0 conflicts
0x23a320fb…cbd7
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:
0x0a2fbf2d…f729b1
1 conflict on slot
0x23c1447bb7…cc456b
Audit this contract →
← previous block
·
next block →
recent activity