pev
.
One block, wave by wave
→
analytics
docs
offline
by Silk Nodes →
pev
/
block
/
#74,360,848
← previous block
next block →
recent activity
Analyzing
Block #74,360,848
9 transactions · 7 stateful · 2026-05-13 16:58:01 UTC
Parallelism
78
/100
Blocked
14
%
Avg conflicts / tx
0.11
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#74,360,848
· 9 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
execute
#2
execute302
· blocks 1
#4
updateDataFeedsValuesPartial
#5
0x6a04ae11
#6
0x98717539
#7
setData
#8
0x39435dac
#3
execute302
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
0xe64f78af…51a7
0x0555e3…2b9c
4 touches
1 conflict
0x00000000…0007
0x0555e3…2b9c
4 touches
1 conflict
0x0b000000…0002
0x000000…1000
2 touches
0 conflicts
0x0711ec2d…d973
0x34b655…2a6f
2 touches
0 conflicts
0x55888ede…6745
0x34b655…2a6f
2 touches
0 conflicts
0x60f7fbaf…bd58
0x34b655…2a6f
2 touches
0 conflicts
0x62d080e9…4a7c
0x34b655…2a6f
2 touches
0 conflicts
0x908d4442…2c4b
0x34b655…2a6f
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:
0x0555e30d…0d2b9c
1 conflict on slot
0xe64f78afd7…e751a7
Audit this contract →
← previous block
·
next block →
recent activity