pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#76,193,535
← previous block
next block →
recent activity
Analyzing
Block #76,193,535
9 transactions · 5 stateful · 2026-05-22 04:59:16 UTC
Parallelism
78
/100
Blocked
20
%
Avg conflicts / tx
0.11
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#76,193,535
· 9 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
updateDataFeedsValuesPartial
#2
setData
#3
execFwdPositionOps
· blocks 1
#4
execFwdPositionOps
#6
execFwdPositionOps
#7
transfer
#8
0x97e2a6…54b0
#5
execFwdPositionOps
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
3
w0
5
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x55890276…60df
0x34b655…2a6f
4 touches
1 conflict
0x18978822…2623
0x34b655…2a6f
4 touches
1 conflict
0xd79c9727…1233
0x34b655…2a6f
4 touches
1 conflict
0x482471ad…122f
0x34b655…2a6f
4 touches
1 conflict
0xc824469a…6425
0x34b655…2a6f
4 touches
1 conflict
0x1be8019f…b769
0x34b655…2a6f
2 touches
0 conflicts
0x48e4e1cf…f91b
0x34b655…2a6f
2 touches
0 conflicts
0x4c344860…c0d0
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
0x55890276a8…ee60df
Audit this contract →
← previous block
·
next block →
recent activity