pev
.
One block, wave by wave
→
analytics
docs
offline
by Silk Nodes →
pev
/
block
/
#74,285,726
← previous block
next block →
recent activity
Analyzing
Block #74,285,726
11 transactions · 9 stateful · 2026-05-13 08:38:19 UTC
Parallelism
82
/100
Blocked
22
%
Avg conflicts / tx
0.18
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#74,285,726
· 11 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
0x0c7abd22
· blocks 1
#2
execute
#3
0x6a0438f3
#5
0x39435dac
· blocks 1
#6
poke
#7
updateDataFeedsValuesPartial
#8
updateDataFeedsValuesPartial
#9
setData
#4
0x1ffa3c9b
#10
0x39435dac
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
1
w0
4
w1
5
w0
10
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x7b7bcac3…8fbf
0x34b655…2a6f
4 touches
1 conflict
0x00000000…003d
0x065c9d…c394
4 touches
1 conflict
0xf00d7a0f…6dc0
0x065c9d…c394
4 touches
1 conflict
0xf823e97f…2ee6
0x065c9d…c394
4 touches
1 conflict
0x546ef093…e6e3
0x065c9d…c394
3 touches
1 conflict
0x79fbd28d…4c33
0x065c9d…c394
2 touches
0 conflicts
0xba6fd619…91c5
0x065c9d…c394
2 touches
0 conflicts
0xcf3283ba…c9fa
0x065c9d…c394
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
0x7b7bcac3fe…968fbf
Audit this contract →
← previous block
·
next block →
recent activity