pev
.
→
showcase
new
graph
analytics
docs
feedback
offline
by Silk Nodes
pev
/
block
/
#77,350,845
← previous block
next block →
recent activity
Analyzing
Block #77,350,845
8 transactions · 7 stateful · 2026-05-27 13:28:39 UTC
Parallelism
63
/100
Blocked
29
%
Avg conflicts / tx
0.38
Longest chain
3
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#77,350,845
· 8 txs across 3 waves · depth 3
parallel ↔ serial
wave
w0
wave
w1
wave
w2
#0
syscallReward
#1
0xab083028
· blocks 2
#4
updatePrices
#5
updateDataFeedsValuesPartial
#6
updateTemporalNumericValuesV1
#7
setData
#2
0xab083028
· blocks 1
#3
0xab083028
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
1
w0
2
w1
3
w2
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x66d63204…51a0
0x69df8a…6292
6 touches
3 conflicts
0xbb8dd99f…bb3f
0x851145…3f07
6 touches
3 conflicts
0x7a12283f…b18a
0x69df8a…6292
6 touches
3 conflicts
0xfd94e24a…9278
0x851145…3f07
6 touches
3 conflicts
0x00000000…003d
0x851145…3f07
6 touches
3 conflicts
0x5a409e7f…09b6
0x69df8a…6292
6 touches
3 conflicts
0x13a54fa2…5ae3
0x2a68ba…90c5
6 touches
3 conflicts
0x8d0d8061…d410
0xc8689a…ee79
6 touches
3 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:
0x69df8a43…506292
3 conflicts on slot
0x66d63204c1…e151a0
Audit this contract →
← previous block
·
next block →
recent activity