pev
.
One block, wave by wave
→
analytics
docs
feedback
offline
by Silk Nodes
pev
/
block
/
#77,490,680
← previous block
next block →
recent activity
Analyzing
Block #77,490,680
8 transactions · 5 stateful · 2026-05-28 05:00:14 UTC
Parallelism
63
/100
Blocked
40
%
Avg conflicts / tx
0.25
Longest chain
3
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#77,490,680
· 8 txs across 3 waves · depth 3
parallel ↔ serial
wave
w0
wave
w1
wave
w2
#0
syscallReward
#1
0xab083028
· blocks 1
#4
forward
#5
updateDataFeedsValuesPartial
#6
updateDataFeedsValuesPartial
#7
setData
#2
0xab083028
· blocks 1
#3
0x3f5c179b
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
0x155f6136…1088
0xa6afd3…d132
4 touches
1 conflict
0x13a54fa2…5ae3
0x2a68ba…90c5
4 touches
1 conflict
0x00000000…003d
0xa6afd3…d132
4 touches
1 conflict
0xbae2ff5d…bf4a
0xa6afd3…d132
3 touches
1 conflict
0xd2e5eb2c…e5db
0xa6afd3…d132
3 touches
1 conflict
0x10abefc9…c9bc
0x69df8a…6292
2 touches
0 conflicts
0x5a409e7f…09b6
0x69df8a…6292
2 touches
0 conflicts
0x66d63204…51a0
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
0x155f613674…711088
Audit this contract →
← previous block
·
next block →
recent activity