pev
.
One block, wave by wave
→
analytics
docs
feedback
offline
by Silk Nodes →
pev
/
block
/
#73,867,412
← previous block
next block →
recent activity
Analyzing
Block #73,867,412
11 transactions · 8 stateful · 2026-05-11 10:12:38 UTC
Parallelism
82
/100
Blocked
13
%
Avg conflicts / tx
0.09
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#73,867,412
· 11 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
0xe2dc7dc3
#2
0xa09e9040
#3
0x0c7abd22
· blocks 1
#4
0xe7be4706
#6
updateTemporalNumericValuesV1
#7
modifyLiquidities
#8
updateDataFeedsValuesPartial
#9
0x6a01ac0e
#10
setData
#5
0x0c7abd22
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
3
w0
5
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x807f2398…fbd4
0xd32edf…ff58
3 touches
1 conflict
0x09000000…0007
0x000000…1000
2 touches
0 conflicts
0x0b000000…0002
0x000000…1000
2 touches
0 conflicts
0x00000000…006f
0x1efe02…37d6
2 touches
0 conflicts
0x0da98b31…3661
0x1efe02…37d6
2 touches
0 conflicts
0x1e270b63…a204
0x1efe02…37d6
2 touches
0 conflicts
0x84a248d0…0fc6
0x1efe02…37d6
2 touches
0 conflicts
0x749437cf…2fc0
0x2880ab…7b43
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:
0xd32edf66…9fff58
1 conflict on slot
0x807f23983e…72fbd4
Audit this contract →
← previous block
·
next block →
recent activity