pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#77,239,569
← previous block
next block →
recent activity
Analyzing
Block #77,239,569
9 transactions · 5 stateful · 2026-05-27 01:07:02 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
#77,239,569
· 9 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
0x1a945f9c
· blocks 1
#2
updateDataFeedsValuesPartial
#3
updateDataFeedsValuesPartial
#4
0x3f5c179b
#5
execFwdPositionOps
#7
execFwdPositionOps
#8
setData
#6
0x366fe5db
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
1
w0
6
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00bac013…a28c
0x91b81b…6d56
4 touches
1 conflict
0xb6b74ae0…8d5e
0xea1b8e…c5ec
4 touches
1 conflict
0x0b000000…0002
0x000000…1000
2 touches
0 conflicts
0x92206814…ec27
0x1efe02…37d6
2 touches
0 conflicts
0x9560013d…8caf
0x91b81b…6d56
2 touches
0 conflicts
0xd991a254…0f62
0x91b81b…6d56
2 touches
0 conflicts
0x00000000…0099
0xaa3145…feec
2 touches
0 conflicts
0x9dc0f3a1…98b6
0xaa3145…feec
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:
0x91b81bfb…8e6d56
1 conflict on slot
0x00bac0131a…bba28c
Audit this contract →
← previous block
·
next block →
recent activity