pev
.
One block, wave by wave
→
analytics
docs
feedback
offline
by Silk Nodes →
pev
/
block
/
#72,288,007
← previous block
next block →
recent activity
Analyzing
Block #72,288,007
12 transactions · 9 stateful · 2026-05-04 02:40:40 UTC
Parallelism
83
/100
Blocked
22
%
Avg conflicts / tx
0.17
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#72,288,007
· 12 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
0x69f8079f
· blocks 1
#2
0x9036287a
· blocks 1
#3
0x69f8079f
#5
0x69f8079f
#6
updateDataFeedsValuesPartial
#7
0x0c7abd22
#9
forward
#10
0x39435dac
#11
setData
#4
0x69f8079f
#8
0x3f5c179b
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
1
w0
2
w0
4
w1
8
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x0d622e34…0000
0x681e90…ae09
4 touches
1 conflict
0x00000000…003d
0x065c9d…c394
4 touches
1 conflict
0x24968e6d…0132
0x065c9d…c394
4 touches
1 conflict
0x03dd7f1d…1ddf
0x065c9d…c394
3 touches
1 conflict
0x8d0da99c…d168
0x065c9d…c394
3 touches
1 conflict
0xa5d2a329…8841
0x065c9d…c394
3 touches
1 conflict
0x74e71984…ae90
0x2a68ba…90c5
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:
0x681e908b…e1ae09
1 conflict on slot
0x0d622e34f9…000000
Audit this contract →
← previous block
·
next block →
recent activity