pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#77,516,754
← previous block
next block →
recent activity
Analyzing
Block #77,516,754
10 transactions · 5 stateful · 2026-05-28 07:53:52 UTC
Parallelism
80
/100
Blocked
20
%
Avg conflicts / tx
0.1
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#77,516,754
· 10 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
0x0f6795d9
· blocks 1
#2
0x0f6795d9
#3
forward
#5
0x0f6795d9
#6
updateDataFeedsValuesPartial
#7
updateDataFeedsValuesPartial
#8
setData
#9
0x044e3d00
#4
0x0f6795d9
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
1
w0
4
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x9a3068dd…18f1
0x34b655…2a6f
4 touches
1 conflict
0x482471ad…122f
0x34b655…2a6f
4 touches
1 conflict
0xc824469a…6425
0x34b655…2a6f
4 touches
1 conflict
0x9a3068dd…18f0
0x34b655…2a6f
4 touches
1 conflict
0x8b36b652…650a
0x34b655…2a6f
3 touches
1 conflict
0xf6884b1c…8b7f
0x34b655…2a6f
3 touches
1 conflict
0x3ee16ca3…b629
0x34b655…2a6f
2 touches
0 conflicts
0x85eb1316…bb9e
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
0x9a3068dd84…9918f1
Audit this contract →
← previous block
·
next block →
recent activity