pev
.
One block, wave by wave
→
analytics
docs
feedback
offline
by Silk Nodes →
pev
/
block
/
#73,926,145
← previous block
next block →
recent activity
Analyzing
Block #73,926,145
11 transactions · 9 stateful · 2026-05-11 16:43:52 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
#73,926,145
· 11 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
0x0c7abd22
· blocks 1
#3
0x5bf9264c
#4
0x5bf9264c
#5
0x1a945f9c
· blocks 1
#7
execute
#8
updateDataFeedsValuesPartial
#9
updateDataFeedsValuesPartial
#10
setData
#2
0x1ffa3c9b
#6
0x366fe5db
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
1
w0
2
w1
5
w0
6
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…003d
0x065c9d…c394
4 touches
1 conflict
0x00bac013…a28c
0xfd44b3…00d1
4 touches
1 conflict
0x0b000000…0002
0x000000…1000
2 touches
0 conflicts
0x031753e2…3ac1
0x065c9d…c394
2 touches
0 conflicts
0x184229dc…04fc
0x065c9d…c394
2 touches
0 conflicts
0x2bed818d…fb08
0x065c9d…c394
2 touches
0 conflicts
0x3605c399…7c1b
0x065c9d…c394
2 touches
0 conflicts
0x890418fd…9c89
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:
0x065c9d28…a9c394
1 conflict on slot
0x0000000000…00003d
Audit this contract →
← previous block
·
next block →
recent activity