pev
.
One block, wave by wave
→
analytics
docs
feedback
offline
by Silk Nodes
pev
/
block
/
#77,351,015
← previous block
next block →
recent activity
Analyzing
Block #77,351,015
10 transactions · 10 stateful · 2026-05-27 13:29:45 UTC
Parallelism
80
/100
Blocked
10
%
Avg conflicts / tx
0.1
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#77,351,015
· 10 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
0x6a16f241
#2
0xed82b078
· blocks 1
#3
updatePrices
#4
updateDataFeedsValuesPartial
#6
0x6df9e92b
#7
setData
#8
0x39435dac
#9
execute
#5
0x3f5c179b
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
2
w0
5
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xd71a331e…42ea
0xa6afd3…d132
4 touches
1 conflict
0xc51d3663…0f45
0xa6afd3…d132
4 touches
1 conflict
0x0b000000…0002
0x000000…1000
2 touches
0 conflicts
0x24cfe713…0f91
0x25d593…7777
2 touches
0 conflicts
0x44ad89ba…cf83
0x25d593…7777
2 touches
0 conflicts
0x24781048…4772
0x2a68ba…90c5
2 touches
0 conflicts
0x76e96198…eec4
0x2a68ba…90c5
2 touches
0 conflicts
0x8876d94c…8435
0x2a68ba…90c5
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:
0xa6afd386…b0d132
1 conflict on slot
0xd71a331efc…0142ea
Audit this contract →
← previous block
·
next block →
recent activity