pev
.
One block, wave by wave
→
analytics
docs
feedback
offline
by Silk Nodes
pev
/
block
/
#77,340,729
← previous block
next block →
recent activity
Analyzing
Block #77,340,729
16 transactions · 14 stateful · 2026-05-27 12:21:22 UTC
Parallelism
88
/100
Blocked
7
%
Avg conflicts / tx
0.06
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#77,340,729
· 16 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
0x0c7abd22
#2
0x0d484c28
#3
0xed82b078
#4
0xed82b078
#5
0xed82b078
#6
updateDataFeedsValuesPartial
#7
updatePriceFeedsIfNecessary
#8
updateFeeds
#9
forward
· blocks 1
#11
forward
#12
forward
#13
forward
#14
0x6a16e239
#15
setData
#10
forward
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
9
w0
10
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…000b
0x10da0c…e102
4 touches
1 conflict
0x09000000…0007
0x000000…1000
2 touches
0 conflicts
0x022ae86a…3125
0x01bff4…1071
2 touches
0 conflicts
0x11b69a7e…334e
0x01bff4…1071
2 touches
0 conflicts
0x56a919c4…ab49
0x01bff4…1071
2 touches
0 conflicts
0x5948f6e6…42c4
0x01bff4…1071
2 touches
0 conflicts
0x78eb0de5…1db2
0x01bff4…1071
2 touches
0 conflicts
0xed67cadc…c62e
0x01bff4…1071
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:
0x10da0c61…e5e102
1 conflict on slot
0x0000000000…00000b
Audit this contract →
← previous block
·
next block →
recent activity