pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#89,761,316
← previous block
next block →
recent activity
Analyzing
Block #89,761,316
7 transactions · 7 stateful · 2026-07-23 23:23:47 UTC
Parallelism
71
/100
Blocked
14
%
Avg conflicts / tx
0.14
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#89,761,316
· 7 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
execFwdPositionOps
#2
0x1fe271b4
· blocks 1
#4
executeBatch
#5
execFwdPositionOps
#6
setData
#3
0x1fe271b4
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
2
w0
3
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…0006
0x0a2fbf…29b1
4 touches
1 conflict
0x1042d3e2…1d72
0x0a2fbf…29b1
4 touches
1 conflict
0x1042d3e2…1d73
0x0a2fbf…29b1
4 touches
1 conflict
0x1042d3e2…1d74
0x0a2fbf…29b1
4 touches
1 conflict
0xa02a1503…b02e
0x0a2fbf…29b1
4 touches
1 conflict
0xa02a1503…b02f
0x0a2fbf…29b1
4 touches
1 conflict
0xa02a1503…b032
0x0a2fbf…29b1
4 touches
1 conflict
0x00000000…0005
0x370e2e…63b4
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:
0x0a2fbf2d…f729b1
1 conflict on slot
0x0000000000…000006
Audit this contract →
← previous block
·
next block →
recent activity