pev
.
One block, wave by wave
→
analytics
offline
by Silk Nodes →
pev
/
block
/
#73,744,420
← previous block
next block →
recent activity
Analyzing
Block #73,744,420
8 transactions · 7 stateful · 2026-05-10 20:28:14 UTC
Parallelism
75
/100
Blocked
14
%
Avg conflicts / tx
0.13
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#73,744,420
· 8 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
0x54cb092e
#2
0x0c7abd22
· blocks 1
#4
updateDataFeedsValuesPartial
#5
0x5339c59f
#6
setData
#7
0x39435dac
#3
0x0c7abd22
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
2
w0
3
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x2b4fceaf…08b3
0xd32edf…ff58
3 touches
1 conflict
0x09000000…0007
0x000000…1000
2 touches
0 conflicts
0x0b000000…0002
0x000000…1000
2 touches
0 conflicts
0x00000000…003d
0x065c9d…c394
2 touches
0 conflicts
0x0ac31945…2c72
0x065c9d…c394
2 touches
0 conflicts
0x529acb6a…fcc6
0x065c9d…c394
2 touches
0 conflicts
0x6135d9cb…d849
0x065c9d…c394
2 touches
0 conflicts
0xad5e269a…89ad
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:
0xd32edf66…9fff58
1 conflict on slot
0x2b4fceafe4…4b08b3
Audit this contract →
← previous block
·
next block →
recent activity