pev
.
One block, wave by wave
→
analytics
offline
by Silk Nodes →
pev
/
block
/
#72,977,863
← previous block
next block →
recent activity
Analyzing
Block #72,977,863
14 transactions · 12 stateful · 2026-05-07 07:17:12 UTC
Parallelism
86
/100
Blocked
17
%
Avg conflicts / tx
0.14
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#72,977,863
· 14 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
execute_route
#2
execute
#3
updateDataFeedsValuesPartial
#4
0x5bf9264c
· blocks 1
#6
forward
#7
0x5339c59f
· blocks 1
#9
0x5339c59f
#10
0xed82b078
#11
0xed82b078
#12
0xeffdedb0
#13
setData
#5
0x5bf9264c
#8
0x5339c59f
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
4
w0
5
w1
7
w0
8
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xea02471d…1539
0x34b655…2a6f
4 touches
1 conflict
0xf2f76ab3…623e
0x2a68ba…90c5
4 touches
1 conflict
0x0b000000…0002
0x000000…1000
2 touches
0 conflicts
0x12309510…0ac2
0x000000…012a
2 touches
0 conflicts
0x7b43f938…3650
0x000000…012a
2 touches
0 conflicts
0x4dd1db39…a994
0x188d58…ea8e
2 touches
0 conflicts
0x4dd1db39…a995
0x188d58…ea8e
2 touches
0 conflicts
0x01a89030…f786
0x368ee5…7ca4
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:
0x34b6552d…112a6f
1 conflict on slot
0xea02471df2…601539
Audit this contract →
← previous block
·
next block →
recent activity