pev
.
One block, wave by wave
→
analytics
docs
feedback
offline
by Silk Nodes
pev
/
block
/
#77,508,924
← previous block
next block →
recent activity
Analyzing
Block #77,508,924
10 transactions · 8 stateful · 2026-05-28 07:01:42 UTC
Parallelism
70
/100
Blocked
25
%
Avg conflicts / tx
0.2
Longest chain
3
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#77,508,924
· 10 txs across 3 waves · depth 3
parallel ↔ serial
wave
w0
wave
w1
wave
w2
#0
syscallReward
#1
0x6df9e92b
#2
0xab083028
· blocks 1
#4
0x5bf9264c
#5
0x5bf9264c
#6
updateDataFeedsValuesPartial
#8
setData
#9
0x884a77…4d5a
#3
0xab083028
· blocks 1
#7
0x3f5c179b
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
2
w0
3
w1
7
w2
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…003d
0xa6afd3…d132
4 touches
1 conflict
0x13a54fa2…5ae3
0x2a68ba…90c5
4 touches
1 conflict
0x0b000000…0002
0x000000…1000
2 touches
0 conflicts
0x44ad89ba…cf83
0x28c888…7777
2 touches
0 conflicts
0x456c8d76…7964
0x28c888…7777
2 touches
0 conflicts
0x93fdd2e2…d459
0x3bd359…433a
2 touches
0 conflicts
0xa472d565…9fe4
0x3bd359…433a
2 touches
0 conflicts
0x10abefc9…c9bc
0x69df8a…6292
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
0x0000000000…00003d
Audit this contract →
← previous block
·
next block →
recent activity